The Advanced Installer Options dialog box contains the following options:

Version

• Version Number —Current software version number the installer uses to determine the action to perform when an installer file already exists on a computer on which you want to deploy a test system. Increment the installer version number when you change the contents of the installer to ensure that the installer overwrites previous installers that exist on the test station computer. The version corresponds to the [ProductVersion] Microsoft Installer (MSI) property.
  Note This control is disabled when the Auto Increment option is enabled.
• Auto Increment —Indicates whether the deployment utility automatically increases the version number when you build an installer to ensure the installer upgrades previous installers on the test station computer. This control is enabled by default, and when enabled, the Version control is disabled.
  Note You must save the deployment before closing the deployment utility to retain the new version number.
• Lock to Deployment Version —Forces the installer to use the same version number as the software version number the deployment utility uses to identify the deployment. If you enable this option, the Version option on the Mode tab determines the installer version number, and the deployment utility automatically increments the installer version number each time you build the installer.
  Note If you enable this option when you are creating a patch deployment installer and the dependent installer version is later than the current deployment software version number, you must increment the deployment software version number so the current patch deployment installer can update the dependent installer.

General Settings

• Installer Executable Name —Specifies the filename of the executable.
• Manufacturer —Name of the company that manufactured the software. This name appears in the standard Windows Control Panel facility for adding and removing programs. This option corresponds to the [Manufacturer] MSI property.
• Upgrade Code —GUID that uniquely identifies a related set of installers in Windows. You can install only one installer, as identified by its unique upgrade code , on a computer at a given time. An installer that specifies the same upgrade code and a later version updates an older installation. When you copy a TestStand deployment specification file ( .tsd ), the file uses the same upgrade code as the original file. Complete the following steps to use a different upgrade code in the file you copied.
  1. Load the .tsd file you copied in the deployment utility.
  2. Click the Installer Options tab and click the Advanced Options button.
  3. Click the Generate button to generate a new upgrade code.
  4. Click OK to accept the changed upgrade code.
  5. Save the .tsd file.
  The upgrade code corresponds to the [UpgradeCode] MSI property.
  Note The Upgrade Code is not available when you create a patch deployment. The deployment utility generates a new upgrade code when the patch deployment depends on a full deployment to ensure the patch installer includes the correct components. Future patch installers that depend on the patch deployment use the same upgrade code to update the new patch installer to ensure the new patch installer does not uninstall required components.
• Generate —Generates a new upgrade code so you can install a newer version of the deployment instead of upgrading an older version of the deployment.
• ReadMe File —Path to a Rich Text Format ( .rtf ) file the installer displays as the Readme for the installer.
• License Agreement —Path to an .rtf file the installer displays as the license agreement for the installer.
• Media Spanning (size in MB) —Maximum size to use for multiple pieces of distribution media when you want to divide an installer that is too large for a single distribution media, such as a CD. Select None to create only a single volume.
• Include Network License Server Settings —Indicates whether the target computer is configured to check out licenses from a network server. Your company must have a Volume License Agreement with National Instruments to use this option. This option also copies the server settings found in the Preferences dialog box of the NI License Manager on the build computer.

TestStand Specific Settings (Requires Inclusion of TestStand Runtime)

• Specify Configuration Directory —Available only when you install the TestStand Engine to configure the deployed TestStand Engine to read configuration files from the locations the Destination and Destination Subdirectory options specify. If a TestStand Engine is already installed on the test station computer, the installer you build with the deployment utility does not change the location TestStand uses to read the configuration files. Use the Preferences tab of the Station Options dialog box to change the configuration directory. You can use multiple configuration directories to support multiple test systems on one computer .
  • Destination —The base directory for configuration files.
  • Destination Subdirectory —The subdirectory, in the directory the Destination option specifies, for configuration files.
• Alternate Association for .seq Files —Available only when you install the TestStand Engine to specify an executable included in the deployment, typically a user interface, to run when a user double-clicks a .seq file in Microsoft Windows Explorer on the test station computer.
  Note The Alternate Association for .seq Files option is available only when you enable the Install TestStand Runtime option on the Installer Options tab of the deployment utility.
• Process Model Used by TestStand Runtime Installer —Use this option to control which process models to use on the computer to which you deploy the TestStand Runtime using an installer you build with the deployment utility. This setting does not change the settings on the development computer.
  • No Change —Uses the default TestStand 2012 or later process models. This setting does not alter the system settings.
  • Force Default Models —Uses the default process models.
  • Force Legacy Models —Uses the equivalent legacy TestStand 2010 process models.
  Note The Process Model Used by TestStand Runtime Installer option is available only when you enable the Install TestStand Runtime option on the Installer Options tab of the deployment utility.
  Note This option is only available in the 32-bit version of the TestStand deployment utility.
• Allow Installer to Upgrade an Installed TestStand Runtime —specifies whether the installer you create for a deployment can upgrade an existing installation of the TestStand Runtime. For example, when you enable this option, an installer that contains the TestStand 2014 Runtime can upgrade an existing installation of the TestStand 2014 Runtime. When you do not enable this option, the installer cannot install a new version of the TestStand Runtime over an existing service pack version of the TestStand Runtime. For example, when you do not enable this option, an installer that contains the TestStand 2014 SP1 Runtime cannot upgrade an existing installation of the TestStand 2014 Runtime. When you do not enable this option, the installer installs drivers and other support files, so you must ensure that those files are compatible with any installed service pack versions of the TestStand Runtime. For example, if you build an installer against TestStand 2014 SP2 and you do not enable this option, you must verify that code modules , sequences, and drivers work correctly with TestStand 2014, TestStand 2014 SP1, and TestStand 2014 SP2. This option is disabled for installers that do not include the TestStand Runtime and for installers that install a non-service pack version of the TestStand Runtime.

Refer to the Microsoft website for more information about MSI properties.

See Also

Deploying TestStand Systems

Patching Deployments

TestStand Deployment Utility