This Document is not yet Rated

Large Scale Software Installation

Primary Software: NI Installers>>Installer Framework
Primary Software Version: 2.6
Primary Software Fixed Version: N/A
Secondary Software: Other NI Software>>NI Volume License Manager

Problem:
How can I automate the installation of different sets of NI software products across different groups of computers at my facility?

Solution:
This method of software installation is intended for automation of the installation process. If end-users will initiate installation of each individual software product, NI recommends building Volume License Installers for each software product (KnowledgeBase 47IAHTQA: Creating a Volume License Installer in VLM).

Software Organization

NI recommends creating one folder on a shared network drive that contains all your National Instruments software installers, such as LabVIEW, TestStand, LabWindows/CVI, device drivers, and the necessary toolkits.

Creating a Batch File

Since one copy of each product is now stored on the network, you can use a batch file to automate installation of a group of NI software products such as Developer Suite Core. The beginning of the batch file should invoke the core software installers, such as LabVIEW, TestStand, and LabWindows/CVI. These items should be followed by the desired toolkits, and then the drivers.

Note: Order of installation is important. Each line in the batch file invokes the installer (setup.exe) of one software product from the network location. An example batch file for installing Developer Suite Core, DevSuiteCore.bat, is shown and attached below. You should create a separate batch file for each group of software you would like to install on a set of computers. Please see KnowledgeBase 4CJDP38M: Automating the Installation of a Single Installer for detailed information on modifying installation behavior with command line arguments.

Advanced Feature: Customizing an Individual Software Product's Installation

A spec file allows you to customize an individual software product's installation without user interaction. For example, you can specify the serial number, user information, individual components of the software to install, and the installation directory. Please see KnowledgeBase 4CJDP38M: Automating the Installation of a Single Installer for information on generating spec files. Notice that in the first line of the batch file above that LV_85.txt is a spec file.

Requesting Permission for Software Licenses
Customers using Volume License Manager should now configure end-users' computers to check-out licenses from the server, instead of a local license file, and to request permission from the server for their specific licenses. This can also be done from the batch file (notice the last two lines of the batch file above). For more information, please see KnowledgeBase 4H38UPXU: Requesting Permissions from VLM during Mass Software Installations.

Warning: You should not invoke MSI components individually from an NI Installer. The NI Installer framework, called from setup.exe handles:

dependencies - each MSI component can have hundreds of dependencies
installation order of MSIs - each group of MSIs has a specific installation order
bookkeeping for software functionality such as LabVIEW Application Builder
maintaining MSI installations when multiple NI software products are installed on the same computer

Installing MSIs individually will likely break functionality of NI software on the Windows installation.

DevSuiteCore.bat

Report Date: 01/04/2008
Last Updated: 10/03/2008
Document ID: 4H3EE0XU

Your Feedback!

Poor | Excellent

Yes

Document Quality?

Answered Your Question?

Please Contact NI for all product and support inquiries.