Managing Software Packages

• Adding MSI/EXE Packages
• Executing Scripts in Software installation
• Modifying MSI/EXE Packages
• Removing MSI/EXE Packages

Desktop Central enables you store the commonly used applications, which can be installed on to the client machines as required. The common applications, which includes both MSI and EXE files, are stored under the Software Packages Repository.

The software packages that are added to the repository can then be used while defining the Software Installation Configuration.

Adding MSI/EXE Packages

Desktop Central allows you to add separate packages for MSI and EXE based software applications:

1. Adding an MSI Package
2. Adding an EXE Package

Adding an MSI Package

1. Click the Software Deployment tab. This invokes the Software Package Repository page listing the details of the packages that have been added.
2. Click the Add Package button.
3. Select the Package type as MSI and specify the following details:
   



Parameter	Description
Package
Package Name	Name of the Software Package
Select the path type	Select any of the following: Network Path: If the software has to be installed in computers in the same LAN, select this option HTTP Path: If the software has to be installed in computers in branch offices over the VPN tunnel or internet, select this option
Add Files to Upload	When you select the HTTP Mode, you need to browse and select the installables, which will be uploaded to the Desktop Central Server
MSI File Name with network path	When you select the Network Path option, specify the name of the MSI file with its complete network path. This path should have all the related files and should have necessary read & execute permissions.   Example: \\MyServer\MSIApps\Skype\skype.msi.
Advanced Options (optional)
Installer / Uninstaller Settings
MSI Root Path	When you choose to copy the installables to individual computers before installing the software, you need to specify the directory to be copied.
MST file name with Network path	For applications that supports customizations prior to installation, you can customize the installation and specify it here. For example, you can customize the MS Office 2003 installation by specifying the license keys, choosing the components to install, etc., using the Microsoft Office Resource Kit Tools. After customization an .MST file gets created. The MST file should also be placed in the network share where all the other installation files are present. Specify the location of the MST file with the network path here. If you are using the copy option while deploying the application, the location of the MST file specified here should be relative to the MSI Root Path. If the MSI Root Path is displayed as \\MyServer\Shares\MSIApps and your MST File is in  \\MyServer\Shares\MSIApps\Office2003\Custom.mst, specify the location as Office2003\Custom.mst. Multiple mst files can be specified as semi-colon separated. Please note that the relative path is required only if you choose to copy the files to the individual computers before installing the software. Else, you can specify the complete network path.
Install Arguments to MSI	Application specific installation parameters can be specified here. For example, for skype, you can specify parameters like installlevel=10. This field can be left blank, if you do not have any application specific arguments.
Uninstall Arguments to MSI	Application specific installation parameters can be specified here. For example, REBOOT=ReallySuppress
Enable Logging for troubleshooting	Select this option to enhance the logging to troubleshooting the deployment errors.
Disable Uninstall option in Add/Remove Programs	Select this option, if you do not want the users to remove the software from Add/Remove Programs.
Package Properties
Manufacturer	Name of the software vendor
Version	The software version
Language	The software language version
Package Description	Description of the software package
Run Script before Installing Software
Script / Command Name	Specify the commands or scripts that has to be executed before installing the software. Refer to Executing Scripts in Software installation for more details.
Arguments	Specify the arguments for the pre-installation script, if any
Continue installation if the exit code is	Select this option and specify the exit code to check for successful pre-installation process before proceeding with the software installation. If the pre-installation fails, the installation will abort.
Run Script after Installing Software
Script / Command Name	Specify the commands or scripts that has to be executed after installing the software. Refer to Executing Scripts in Software installation for more details.
Arguments	Specify the arguments for the post-installation script, if any.
Successful if the Exit Code is	Select this option and specify the exit code to verify whether post installation has been successful. If post-installation is not successful, the software will not be uninstalled.
Run Script before Uninstalling Software
Script / Command Name	Specify the commands or scripts that has to be executed before uninstalling the software. Refer to Executing Scripts in Software installation for more details.
Arguments	Specify the arguments for the pre-uninstallation script, if any
Continue uninstallation if the exit code is	Select this option and specify the exit code to check for successful pre-uninstallation process before uninstalling of the software.  If the pre-installation fails, the uninstallation will abort.
Run Script after Uninstalling Software
Script / Command Name	Specify the commands or scripts that has to be executed after uninstalling the software. Refer to Executing Scripts in Software installation for more details.
Arguments	Specify the arguments for the post-uninstallation script, if any.
Successful if the Exit Code is	Select this option and specify the exit code to verify whether post uninstallation has been successful. If post-installation is not successful, the software will not be re-installed.



4. Click Add Package. The package gets added to the table below.
5. Repeat steps 3 to 5 for adding more packages.

Top

Adding an MSIEXEC/EXE/ISS/Command Package

1. Click the Software Deployment tab. This invokes the Software Package Repository page listing the details of the packages that have been added.
2. Click the Add Package button.
3. Select the Package type as MSIEXEC /EXE/ISS/Command and specify the following details:
   
    

   Parameter	Description
   Package
   Software Name	Name of the Software Application. Click on the Select from Pre-Defined Application link. This opens the Select Application dialog. You can make your selection from the pre-defined packages that are listed. Alternatively, you can also select from the prompted list, while typing the application name in the text field.
   Select the path type	Select any of the following: Network Path: If the software has to be installed in computers in the same LAN, select this option HTTP Path: If the software has to be installed in computers in branch offices over the VPN tunnel or internet, select this option
   Add Files to Upload	When you select the HTTP Mode, you need to browse and select the installables, which will be uploaded to the Desktop Central Server
   Installation Command with switches/arguments	Specify the command to be executed in the client computers for installing the application. The command specified here will be "as such" executed in all the client computers. Make sure that the path to the executables specified in the command is relative to the EXE Root Directory specified above. Examples:    1. msiexec.exe \Skype\skype.msi /qn    2. googlesetup.exe /S
   Uninstallation Command with switches/arguments	Specify the command to be executed in the client computers for uninstalling the application. The command specified here will be "as such" executed in all the client computers. Make sure that the path to the executables specified in the command is relative to the EXE Root Directory specified above. Example:Skype\uninstall.exe If the uninstaller in the individual computers has to be invoked, you can specify the complete path to the uninstaller. please note that the uninstaller has to be in the same location in all the client computers. You can use environment variables in the path. Examples: C:\WINDOWS\ie7\spuninst\spuninst.exe /q %SystemRoot%\ie7\spuninst\spuninst.exe /q
   Advanced Options (optional)
   Installer / Uninstaller Settings
   EXE Root Path	When you select the Network Path option, specify the shared directory from where all the commands will be executed. This directory should have access to all the executables that are required to install the application.
   Package Properties
   Manufacturer	Name of the software vendor
   Version	The software version
   Language	The software language version
   Package Description	Description of the software package
   Run Script before Installing the Software
   Script / Command Name	Specify the commands or scripts that has to be executed before installing the software. Refer to Executing Scripts in Software installation for more details.
   Arguments	Specify the arguments for the script, if any
   Continue installation if the exit code is	Select this option and specify the exit code to check for successful pre-installation process before proceeding with the software installation. If the pre-installation fails, the installation will abort.
   Run Script after Installing the Software
   Script / Command Name	Specify the commands or scripts that has to be executed after installing the software. Refer to Executing Scripts in Software installation for more details.
   Arguments	Specify the arguments for the script, if any
   Successful if the Exit Code is	Select this option and specify the exit code to verify whether post installation has been successful. If post-installation is not successful, the software will not be uninstalled.
   Run Script before Uninstalling the Software
   Script / Command Name	Specify the commands or scripts that has to be executed before uninstalling the software. Refer to Executing Scripts in Software installation for more details.
   Arguments	Specify the arguments for the script, if any
   Continue uninstallation if the exit code is	Select this option and specify the exit code to check for successful pre-uninstallation process before uninstalling of the software. If the pre-installation fails, the uninstallation will abort.
   Run Script after Uninstalling the Software
   Script / Command Name	Specify the commands or scripts that has to be executed after uninstalling the software. Refer to Executing Scripts in Software installation for more details.
   Arguments	Specify the arguments for the script, if any
   Successful if the Exit Code is	Select this option and specify the exit code to verify whether post uninstallation has been successful. If post-installation is not successful, the software will not be re-installed.

    
4. Click Add Package. The package gets added to the table below.

5. Repeat steps 3 to 5 for adding more packages.

Top

Executing Scripts in Software Installation

Desktop Central allows you to execute scripts in the following cases:

• Prior to installing the software
• After installing the software
• Prior to uninstalling the software
• After uninstalling the software.

The following needs to be ensured while you specify a script to be executed in any of the above cases:

1. The scripting engine should also be specified in the Script/Command field. For example, if you are specifying a vb script, say test.vbs, you should specify like this: %SystemDrive%\Windows\cscript \\dc-win2k1\scripts\test.vbs. In this case the cscript should be in the same location in all the client computers. Alternatively, you can also specify the engine path in a network share like: \\dc-win2k1\Windows\cscript \\dc-win2k1\scripts\test.vbs
2. When you select the Copy option while defining the Install Software Configuration, the following needs to be taken care:
   1. When selecting None: the script file should be in the network share.
   2. When selecting Copy file to client machines: the script should be in the network share.
   3. When selecting Copy folder to client machines: The script should be in the same directory or sub-directory as that of the installation file and the path specified should be relative path from that directory.
3. When using absolute path, use the environment variables instead of specifying the path directly. For example, for c: use %SystemDrive%.

Modifying MSI/EXE Packages

To modify the MSI/EXE packages, follow these steps:

1. Click the Admin tab to invoke the Admin page
2. Click the Software Repository link in the Admin Links pane.
3. Click the icon under the Actions column next to corresponding package.
4. Follow the step 4 and step 5 of the Adding MSI/EXE Packages procedure.
5. Click the Modify Package button.

Removing MSI/EXE Packages

To remove the MSI/EXE packages, follow these steps:

1. Click the Admin tab to invoke the Admin page.
2. Click the Software Repository link in the Admin Links pane.
3. Click the icon under the Actions column next to corresponding package. Click OK to confirm deletion.

The package details will be deleted from the table.

Top