Preparing for deployment

Preparing the Software deployment list

Select a deployment method for all software on your Software deployment list by clicking one of the method icons above the list, or select methods for each software individually.

Before deploying a program, you need to create at least one deployment package, as well as select program bitness in the Software editor.

A program without any deployment packages, or without any having been selected, will not be deployed.

Preparing the Deployment targets list

When a device has been scanned successfully for the first time, the login that provided access becomes attached to it automatically. It's possible to switch to another login or create a new one from the Deployment targets list.

Logins are set in the same way as in the Scanner.

Readiness for deployment

The necessary conditions for deployment are as such:

  1. Software has been added to the Software deployment list.
  2. A computer or several have been added to the Deployment targets list.
  3. A deployment method is selected in the Software deployment list.

If one or several of the conditions have not been met, TSD will inform you accordingly.

The deployment tree and possible conflicts

One of the main elements of the Deployment desktop is the Deployment tree: an area consisting of a table structure, with rows representing computers from the Deployment targets list, while software from the Software deployment list is represented by columns. The cells of the table show the deployment status of each software for each computer.

By hovering over an icon in the  Deployment tree cell, you'll be able to read a description of the alert or error in a hint. This information is also displayed in the Deployment log.

If TSD encounters a conflict, it will display a warning or an error.

Possible warnings:

  • If the Macro deployment package was created on a Windows version newer than Vista and the target computer operates on a version older than Windows Server 2003 (or vice versa), TSD will display a warning. For exampleThis macro was recorded on Windows 8 operating system. It may be incompatible with Windows Server 2003This occurs because windows and controls may be displayed differently on different operating systems. In such cases, TSD may erroneously consider a window or control missing, which will prevent the service from interacting with them.
  • If the Sysshot deployment package was created on an OS with architecture different from the target computer's OS's, TSD will display a warning. For exampleThis sysshot was recorded on 64-bit operating system. It may be incompatible with 32-bit architecture. This occurs due to some differences in the registries of OS'es with different architectures.

Possible errors:

  • When attempting to deploy to a computer operating on Windows 2000 or olderFor exampleSilent install method is incompatible with Windows 2000.
  • When attempting to deploy a 64-bit application to a computer operating on a 32-bit OSFor exampleThis software is a 64-bit application. It is incompatible with Windows XP 32-bit.