You can use the TestStand Deployment Utility with custom commands to build a single MSI-based installer that installs all the components of a test system, such as sequences, step types, code modules, support files, user interfaces, NI drivers, run-time engines, and third-party drivers.

Use the Custom Commands dialog box to configure commands the MSI-based installer executes after all files have been installed, such as launching an installer you built with LabVIEW or LabWindows/CVI, a third-party installer, or an installer for a user interface.

Requiring users to sequentially run multiple installers for third-party or separate components of the test system forces users to wait for each installer to complete before running the next installer. This process can introduce errors if users do not run the installers in the correct order.

Use custom commands to accomplish the following tasks:

• Run a single installer to install the entire test system and any required third-party installers
• Serialize the execution of multiple installers in the order you configure in the deployment utility
• Request a reboot after all commands execute
• Display a progress window to aid in debugging installation issues
• Use macros in command-line arguments to pass TestStand-specific directories to a third-party installer. For example, the <TESTSTAND> macro corresponds to the <TestStand> directory for the version of TestStand you used to build the installer.