Software passport

Filling in software information

Total Software Deployment imports basic software information from the installer. Verify the information and fill in the empty fields in the Software passport.

Here you can specify:

  • The displayed name;
  • Program version;
  • Program bitness;
  • Program’s installation context;
  • Deployment verification file;
  • Software search string.

Also, the passport allows to:

  • Update the software installer;
  • Load an alternative icon;
  • Add a note;
  • Add add-on or update installers etc.

Information from the Version and Software name search fields is used by the Assistant for searching software on network computers. Special characters that can be used for advanced search in the trees have the same effect here. The Software name search string is also used when editing System shot deployment packages.

Updating the installer

Once in a while, you may need to replace a software installer in the Software storage, for example, when a new version comes out. You can do this by clicking Update installer in the Software passport or in the context menu of the Software tree:

If the installer consists of more than one file, tick the checkbox and point to the installer folder.

After the installer is updated, the following fields in the passport will be changed: the displayed name (if it hasn’t been changed manually) and version.

If a particular program already has a Macro and/or System shot recorded, and its installer is updated, then they will need to be re-recorded. The Silent package will be automatically updated if the installer’s format is changed.

Program bitness

Program bitness is one of the most important factors during deployment. It’s important to set correct bitness to safeguard from possible errors if the wrong deployment target was selected.After adding a program to the Software storage, select its bitness by clicking Set program’s bitness in the passport. Software with no bitness set is not allowed to be deployed.

We recommend making sure that bitness is correct for the installed program before setting it. Deployment of 64-bit programs on 32-bit operating systems using System shot can lead to unforeseen consequences, up to and including OS failure on the target node (deployment of 32-bit software on 64-bit operating systems is normal). When deploying using the other methods, correct bitness setting will save you from receiving additional irritating deployment errors, since 64-bit software will most likely not be installed on a 32-bit OS.

If you’re not sure whether your program is 32-bit or 64-bit, you can let TSD detect it from the executable if the program is installed locally. In this case, it’s most convenient to do it after a local Silent test run or after recording a macro or making a system shot. To do this, click Check for me and browse to the program’s executable file.

Some installers may be able to install both the 32-bit and the 64-bit version of the program and establish a program of the same bit depth as that of the operating system on which they were launched. For such installers, we recommend setting the bitness at 32 bit.

Do not detect bitness based on the installer: it may have different bitness than the program it installs. For example, a 32-bit installer may install 64-bit software.

Installation context

When the installer is run, one of the main parameters is the installation context. Before setting the installation context, you need to check what kinds of installation are supported by the installer. You can read here to find out how to correctly determine the installation context for software. If the deployment package is created for per-machine installation, then you have to select Local system privileges. Some programs do not support installation for all users: you need to select the Current user context in these cases. For scripts that require network administrator privileges, you have to select the Administrator context.

Verification file

You can provide a path to the deployment verification file. This allows you to more correctly determine the result of software deployment. After the deployment is completed, TSD checks for changes to the file via the specified path and displays a message in the Deployment log showing the type of change (added, changed, deleted, or no changes).


The list of add-ons allows adding additional installers for add-ons, updates, etc.

The buttons under the list allow to add, remove and update installers from the list and change the installation order. You can add more than one file at the same time.

Installers located in the list of add-ons will automatically be added to the deployment package. When recording the package, additional installers will automatically start after the main installer.

If a particular program already has a Macro and/or System shot recorded, and the list of add-ons is modified, then they will need to be re-recorded. The Silent package will not be affected.