When deploying and installing a new installation item the following should be determined:
1 – Naming convention
2 – Automatic (unattended) installation

Naming convention
Determining the name of an application is one of the most important things when adding a new installation item. Consider that the installation item in the future probably will be updated before it will be removed. The name of the installation item is what makes this installation item unique to the installation list and all running ‘Easy Software Deployment Agents’. It is best practice to at least add the name and the major version of the installation item when adding a new installation item to the installation list.

<Application Name> <Application Major Version>

An example would be:

Adobe Reader 9

When this installation item is replaced or updated by a newer version a new installation item would be called:

Adobe Reader 10

Since a new application item will have new source files it is best practice to use the same name for the folder or directory that will share the source files on the network. An example source directory would be:

\Application_ServerApplicationsAdobe Reader 9
\Application_ServerApplicationsAdobe Reader 10

Automatic installation
Determining how a new installation item is installed, repaired and removed unattended is needed to ensure a successful control of this installation item in your network. Consult the installation manual from the software vendor to determine how the application is (silently) installed and how this application is being updated or removed in the future. When the installation item exists out of one or more Microsoft Installer Files (*.msi) a default silent installation string will be generated by the ‘Easy Software Deployment Manager’ when adding this installation item to the installation list.

If the software vendor does not provide any information on how the software will be installed unattended you should consider scripting or repackage the software. If you deploy the software attended make sure the software is deployed only when a user is logged on and interaction is possible.