From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Example Code

How Can I use Microsoft SMS to Deploy NI Software

Problem:

What is the most efficient way to deploy NI software to my different groups of computers? I have already created a batch file to invoke my different NI installers, as documented in Requesting Permissions from NI VLM during Mass Software Installations.

Solution:

In order to automate the deployment of software to your computers, NI recommends using an enterprise software management tool (e.g. Microsoft SMS). The following instructions explain how to use Microsoft SMS 2003 or SCCM 2007 to deploy custom batch files:

  • Create one package for all related NI installers. The package source files should reference a network share or local directory of common NI installer files.
  • Create a program for each batch file or custom installation script. All programs should be dependent upon the common source files contained in the above package.
  • For each program, create an advertisement to specify when you would like the batch file to run.
  • For each advertisement, specify a collection. A collection is a group of computers on which you will install the NI software invoked in the program.

For additional information regarding software deployment with Microsoft SMS, refer to the following documentation:

Note: You should not invoke MSI components individually from an NI Installer. Rather, use a batch file to invoke each installer's setup.exe as outlined in Requesting Permissions from NI VLM during Mass Software Installations. 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 Application Builder in LabVIEW
  • maintaining MSIs installations when multiple NI software products are installed on the same computer.

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

Related Links:

KnowledgeBase 4H38UPXU: Requesting Permissions from NI VLM During Mass Software Installations
KnowledgeBase 4H3EE0XU: Large Scale Software Installation
KnowledgeBase 4CJDP38M: Automating the Installation of National Instruments Software
KnowledgeBase 47IAHTQA: Creating a Volume License Installer in NI VLM
MyITForum.com: Important notes on running .BAT files from UNC in SMS/SCCM

Tutorial,en,en,

Cheers,

David Goldberg
National Instruments
Software R&D

Example code from the Example Code Exchange in the NI Community is licensed with the MIT license.

Comments
johnlimejk
Member
Member
on

To use Microsoft System Center Configuration Manager (SCCM) to deploy National Instruments (NI) software, you can follow these general steps:

  1. Create a package in SCCM: In SCCM, create a new package and specify the location of the NI software installer files.

  2. Distribute the package: Distribute the package to distribution points so that client computers can access it.

  3. Create a program: Create a program within the package to specify the installation command for the NI software. This command may include any necessary command line switches and arguments.

  4. Create a collection: Create a collection in SCCM to target the deployment to a specific set of client computers.

  5. Deploy the package: Deploy the package to the collection you created in step 4. SCCM will then push the installation command to the targeted client computers, and the NI software will be installed.

Note that the exact steps may vary depending on the version of SCCM and the specific NI software being deployed. It's recommended to consult the documentation for both SCCM and the NI software for detailed instructions.

 

Source: SMSala Bulk SMS Service

Contributors