HomeSupport KBAdvanced (Technical)How To Automate The Deployment

1.8. How To Automate The Deployment

See below for information to help with automated deployment using AutoID, a login script, or your existing software deployment system:

Silent Installation:

The following command will install the software without any interaction or visible windows:

C:\TrainingManagerEnterpriseSetup.exe /SP- /VERYSILENT /SUPPRESSMSGBOXES /NOCANCEL

The command above is for the case with the setup file located at the root of the C drive (C:\). Modify the first part of the command to reflect the location of the setup file for your case.

See additional setup file command line parameters at the following link:

Command Line Parameters 

License Key:

To automate the license key configuration, you will need to copy the EntLicense.lic file from a licensed machine, and use it as the source to copy to new installations. It is located in the Windows-defined all users application data directory. See the file locations here:

File Locations

Database Connection:

Option 1:

If the installation location will be the same on all machines, you can create a shortcut with the server path hard coded in the properties (as you may have seen in the user guide - Command Line Parameters), and then copy that shortcut to each user's desktop. However, the default installation path will vary depending on whether the machine is 32 or 64 bit.

Option 2:

Updating the config files can also be done. The way it works is that there is a config file in the installation directory which contains default values for the user config file. On the first time the application is run, it will create a user.config file in the users profile folder using the values from the .config file in the installation directory. Subsequent changes to the users configuration will be saved in the user.config file. Note that the user.config file is located in a sub-directory of the user's profile folder, and the sub-directory includes a GUID which is unique for that machine. See the "File Locations" link above.

To deal with the uniqueness, you can change the default config file in the installation directory. Note that this change must be made before the application is opened the first time, because the user.config file will be created on the first run only.

You can find information about each of these options at the following link:

Citrix options for hardcoding server path


Knowledge Tags

This page was: Helpful | Not Helpful