Clean install

[rik_aspinall]

Hi Folks,

Here is a terribly embarrassing question, because it seems both so hard and so simple at the same time:

I would like to install Labview (and many packages) on many machines (all the same config). I would like to 

a) Remove the old version

b) Install the new version(s) based on the VLA server

Currently here's what I have to do:

a) Click through a million packages that were installed and uninstall them via the Add/Remove programs utility

b) Download terrabytes of new labview (2DVD's+1 driver CD)

c) Carefully select the options I need from said discs

d) Rinse and repeat every 6 months

I am sure there are many tricks I am missing. The one thing I do know is that I do no want to happily coexist with the old version - just way too much space and hard to decode interdependency (for an example, try uninstalling say VISA 14 and you will be told to remove VISA 5.4.x also).

I'd also love a concise guide to what each package is and why I might need it - a family tree if you will.

Thanks for your help!

Rik

PS. There is some reference to a post concerning "MSI blast" which is not helpful as the tool has been removed

[crossrulz · Accepted solution]

---

@rik_aspinall wrote:

d) Rinse and repeat every 6 months

---

That should be once a year.  The service pack will install over the base version.  So you should only just have to install the SP (no uninstalling required).

[JÞB]

b) Install the new version(s) based on the VLA server

---

Just stuff in DVD1 with autoplay.  At the prompt "Select software to install based on previously installed license"  have a connection to NI.com available.

Easy as 3.14159 

[rik_aspinall]

Ah, a problem halved...now I just received LV2014DS2 - would that imply that the once a year would be now or in August? I may be wrong but from last August I got LV2013SP1, so I now have LV2014. So would I switch now (at the release of LV2014?) or in August (apparently the calendar year for NI's support cycle)?

Thanks,

Rik

[rik_aspinall]

I'm not sure if this is the same as the online installer, but I do not have a license code as such with the VLA. This means that I am encouraged to either install an evaluation version or enter a serial number - or am I somehow missing a serial number for the VLA?

[crossrulz]

NI releases their new version of LabVIEW in August at NI Week.  So 2013 SP1 came in the March timeframe.  2014 can out in August.  If you wait a few more months, you will have 2014 SP1 (February-March timeframe is typical).  A lot of people just use the SP versions of LabVIEW.  So that could cut down on your work even more.

[crossrulz]

A VLA has a license number.  You should talk to your administrator for it.  Or, if you are the administrator, take a look at the packaging your Developer Suite disks come in.  There should be a license number written down somewhere.

[JÞB]

---

@crossrulz wrote:

A VLA has a license number.  You should talk to your administrator for it.  Or, if you are the administrator, take a look at the packaging your Developer Suite disks come in.  There should be a license number written down somewhere.

---

OR:  Menu>>Help>>About LabVIEW from ant FP, BD, LLB explorer, Project Explorer or Getting Started Window. (any LabVIEW window with a menu.... Kudos to anyone who can find an exception that is default LabVIEW behavior) 

The current License is displayed in the About.vi

The Exception is if you switch from a single seat to a VLA.  Then the single seat key will still display in "About.vi" but the NI License Manager will show the correct key.

[TBirkulosis · Accepted solution]

You mention that you have a VLA Server. If you are using NI Volume License Manager (VLM) you can create a Volume License Installer (VLI). If you know exactly which software, modules, and toolkits you need, you can use the NI Batch Installer Builder to select the software you need and then create a VLI with that customized selection. Here is a link to the help manual for Batch Installer Builder.

You may already have tools to automate installation, but we do have some KnowledgeBase articles that discuss automating installation and automating licensing (see "Silently point a computer to a volume license server to check out licenses.").

I hope these tools and articles help you get started. I'm don't know off the top of my head a way to automate uninstalling programs, but these should at least help you streamline the installation process.

[rik_aspinall]

Thanks everyone and in particular Taylor

I also realized that I could select multiple items to uninstall (duh!) which expedites a lot.

The last question I have would be if anyone knows of an overview guide to the legion of little bits of code that are separate items in the NI installer package. It would really help me to understand why things have been installed, and perhaps start to appreciate why when something so broad as say VISA exists it would still install these packages individually.