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 language;
- Program bitness.
Also, the passport allows to:
- Load an alternative icon;
- Open the folder containing the program installer and other data in Explorer;
- Set a software search string;
- 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. The Software name search string is also used when editing System shot deployment packages.
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. If bitness has not been set, TSD will keep prompting you to set it during editing. Programs with unset bitness will not be allowed to be deployed.
We recommend to make 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 to set 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.
When deploying using the default settings, TSD checks whether there's an active user on the target computer and returns an error if not. This is important because the default installation context for most installers is "per-user". If you are certain that the program will be deployed per-machine (for all users), you can enable the Logged in user not required setting, and TSD will skip the check. Detailed information is available in the Installation context section.
The list of add-ons allows to add additional installers for add-ons, updates etc.
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.
The buttons under the list allow to add and remove installers from the list and change the installation order.
If Macro and/or System shot methods have already been recorded for a particular program, then editing the list of add-ons will necessitate rerecording of these methods. Silent installation will not be affected.