NI Home
Cart Cart | Help
Company Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI

Currently Being Moderated

How Can I use Microsoft SMS to Deploy NI Software

VERSION 2

Created on: Dec 12, 2008 11:17 AM by AEDavid - Last Modified:  Dec 12, 2008 11:26 AM by AEDavid

 

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

Average User Rating
(0 ratings)




There are no comments on this document