Deploy Global Configuration Settings with TestStand Deployment Utility

Updated Nov 3, 2017

Reported In


  • TestStand 2016 SP1
  • TestStand 2016
  • TestStand 2014 SP1

Issue Details

I am creating a TestStand deployment using the TestStand Deployment Utility. I would like to include global settings such as Station Globals, Search Directories, and Tools Menu items in the deployment. How should I configure the TestStand Deployment Utility to achieve that?


Global settings like Station Globals, Search Directories, and Tools Menu configuration are stored in configuration files in the TestStand Cfg directory, which is located in <TestStand Application Data>\Cfg for TestStand 4.1 and later, or <TestStand>\Cfg for TestStand 4.0 and earlier. You must include these files in your deployment unless you want to deploy the default settings.

By default, the files in the TestStand Cfg directory are not included in the TestStand Deployment.  In order to ensure that these configuration files are included in your deployment, you must include these files in your workspace, then select them in the Distributed Files tab of the TestStand Deployment Utility.

Please note that the StationGlobals.ini and other config files located in the TestStand Cfg directory will not be automatically included by simply checking the Deploy Files in TestStand Public Directories option. Even if this option is checked, you must include the desired files in your workspace and deploy as normal.

TestStand 2016 and later supports deploying with environments through the TestStand Deployment Utility. TestExec.ini was also refactored into several smaller configuration files in TestStand 2016. For more information about the TestExec.ini refactoring please see the Refactored TestExec.ini File page.


Not Helpful