Managing Software Packages


Desktop Central enables you to store the commonly used applications which can be installed on to the client machines as required. The common applications that include MSI, EXE, APPX and MSU files are stored in the Software 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. Navigate to Software Deployment tab and click Add Packages.

  2. Select the Package type as MSI and specify the following details:

     

    Parameter

    Description

    Package

    Package Name

    Name of the Software Package

    License Type

    Specify if the software is commercial or non-commercial

    Locate installable

    The installable needs to located -

    • From Shared Folder : If the software has to be installed in computers in the same LAN, select this option

    • From Local Computer : 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 choose to locate the installable from local computer, 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 to choose the installable from shared computer, 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.

    MSI Properties for installation

    Specify the MSI properties for installation.

     

    Example: REBOOT=ReallySuppress

    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.

    Pre-Deployment Activities before Installation

    Check if Software Exists

    Specify the Software Name and version, based on the search result you can choose to proceed with the installation, uninstall the existing version or skip installation.

    Check Registry Key/Value

    Specify the Header Key, Sub Key and Value Name, based on the search result you can choose to proceed with the installation, uninstall the existing version or skip installation.

    Check Data on Registry Value

    Specify the Header Key, Sub Key,  Value Name, Data Type, Comparator and Register value,  based on the search result you can choose to proceed with the installation, uninstall the existing version or skip installation.

    Check File Folder

    Specify the File Name or Folder Name based on the search result you can choose to  proceed with the installation, uninstall the existing version or skip installation.

    Check Free Disk Space

    Specify the required free space and the drive, so that installation will be initiated only if there is sufficient space.

    Check Running Process

    Specify the Process Name, so that you can choose to proceed with the installation when the process is stopped or kill the process and proceed with the installation.

    Configurations

    Configurations such as Create/Append Path, Create/Delete Shortcut, Executing custom scripts, Managing Files and Folders, Configuring Registry Settings and Configuring Windows Services, Setting Environment Variables can be deployed as a pre-deployment activity.

    Configurations

    Configurations such as Create/Append Path, Create/Delete Shortcut, Executing custom scripts, Managing Files and Folders, Configuring Registry Settings and Configuring Windows Services, Setting Environment Variables can be deployed as a post-deployment activity.

    Pre-Deployment Activities before Uninstallation

    Check if Software Exists

    Specify the Software Name and version, based on the search result you can choose to  proceed with the installation, uninstall the existing version or skip installation.

    Check Registry Key/Value

    Specify the Header Key, Sub Key and Value Name, based on the search result you can choose to  proceed with the installation, uninstall the existing version or skip installation.

    Check Data on Registry Value

    Specify the Header Key, Sub Key,  Value Name, Data Type, Comparator and Register value,  based on the search result you can choose to  proceed with the installation, uninstall the existing version or skip installation.

    Check File Folder

    Specify the File Name or Folder Name based on the search result you can choose to proceed with the installation, uninstall the existing version or skip installation.

    Check Running Process

    Specify the Process Name, so that you can choose to proceed with the installation when the process is stopped or kill the process and proceed with the installation.

    Configurations

    Configurations such as Create/Append Path, Create/Delete Shortcut, Executing custom scripts, Managing Files and Folders, Configuring Registry Settings and Configuring Windows Services, Setting Environment Variables can be deployed as a pre-deployment activity.

    Post-Deployment Activities after Uninstallation

    Configurations

    Configurations such as Create/Append Path, Create/Delete Shortcut, Executing custom scripts, Managing Files and Folders, Configuring Registry Settings and Configuring Windows Services, Setting Environment Variables can be deployed as a post-deployment activity.

    Advanced Options

    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.

    Architecture Specify the Package architecture as 62 bit or 32 bit. If the software architecture is chosen as 32 bit , then it will be installed on all the computers (32 bit and 64 bit). If the software architecture chosen is 64 bit, then Desktop Central will not try to install the software on 32 bit computers.
    Maximum Time Limit for Installation Specify the time limit allowed for the installation to happen. If the time to install the software application exceeds the time limit specified here, installation process will be aborted.

    Enable Logging for troubleshooting

    Select this option to enhance the logging to troubleshooting the deployment errors.

    Package Properties

    Manufacturer

    Name of the software vendor

    Version

    The software version

    Language

    The software language version

    Package Description

    Description of the software package

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

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

Adding an MSIEXEC/EXE/ISS/Command Package

  1. Navigate to Software Deployment tab and click Add Packages.

  2. Select the Package type as MSIEXEC /EXE/ISS/Command and specify the following details:

     

    Parameter

    Description

    Package

    Package Name

    Name of the Software Package

    License Type

    Specify if the software is commercial or non-commercial

    Locate installable

    The installable needs to located -

    • From Shared Folder : If the software has to be installed in computers in the same LAN, select this option

    • From Local Computer : 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 choose to locate the installable from local computer, 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

     

    Pre-Deployment Activities before Installation

    Check if Software Exists

    Specify the Software Name and version, based on the search result you can choose to proceed with the installation, uninstall the existing version or skip installation.

    Check Registry Key/Value

    Specify the Header Key, Sub Key and Value Name, based on the search result you can choose to proceed with the installation, uninstall the existing version or skip installation.

    Check Data on Registry Value

    Specify the Header Key, Sub Key,  Value Name, Data Type, Comparator and Register value,  based on the search result you can choose to proceed with the installation, uninstall the existing version or skip installation.

    Check File Folder

    Specify the File Name or Folder Name based on the search result you can choose to  proceed with the installation, uninstall the existing version or skip installation.

    Check Running Process

    Specify the Process Name, so that you can choose to  proceed with the installation when the process is stopped or kill the process and  proceed with the installation.

    Configurations

    Configurations such as Create/Append Path, Create/Delete Shortcut, Executing custom scripts, Managing Files and Folders, Configuring Registry Settings and Configuring Windows Services, Setting Environment Variables can be deployed as a pre-deployment activity.

    Post-Deployment Activities after Installation

    Configurations

    Configurations such as Create/Append Path, Create/Delete Shortcut, Executing custom scripts, Managing Files and Folders, Configuring Registry Settings and Configuring Windows Services, Setting Environment Variables can be deployed as a post-deployment activity.

    Pre-Deployment Activities before Uninstallation

    Check if Software Exists

    Specify the Software Name and version, based on the search result you can choose to  proceed with the installation, uninstall the existing version or skip installation.

    Check Registry Key/Value

    Specify the Header Key, Sub Key and Value Name, based on the search result you can choose to  proceed with the installation, uninstall the existing version or skip installation.

    Check Data on Registry Value

    Specify the Header Key, Sub Key,  Value Name, Data Type, Comparator and Register value,  based on the search result you can choose to  proceed with the installation, uninstall the existing version or skip installation.

    Check File Folder

    Specify the File Name or Folder Name based on the search result you can choose to proceed with the installation, uninstall the existing version or skip installation.

    Check Running Process

    Specify the Process Name, so that you can choose to proceed with the installation when the process is stopped or kill the process and proceed with the installation.

    Configurations

    Configurations such as Create/Append Path, Create/Delete Shortcut, Executing custom scripts, Managing Files and Folders, Configuring Registry Settings and Configuring Windows Services, Setting Environment Variables can be deployed as a pre-deployment activity.

    Post-Deployment Activities after Uninstallation

    Configurations

    Configurations such as Create/Append Path, Create/Delete Shortcut, Executing custom scripts, Managing Files and Folders, Configuring Registry Settings and Configuring Windows Services, Setting Environment Variables can be deployed as a post-deployment activity.

    Advanced Options

    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.

    Exit Code Specify the exit code, which should be returned when the installation has been succeeded.
    Architecture Specify the Package architecture as 62 bit or 32 bit. If the software architecture is chosen as 32 bit , then it will be installed on all the computers (32 bit and 64 bit). If the software architecture chosen is 64 bit, then Desktop Central will not try to install the software on 32 bit computers.
    Maximum Time Limit for Installation Specify the time limit allowed for the installation to happen. If the time to install the software application exceeds the time limit specified here, installation process will be aborted.

    Package Properties

    Manufacturer

    Name of the software vendor

    Version

    The software version

    Language

    The software language version

    Package Description

    Description of the software package

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

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

Modifying MSI/EXE Packages

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

  1. Click Software Deployment tab.

  2. The list of managed packages , will be displayed.

  3. Click the Actions column next to corresponding package.

  4. Select Modify to modify the package.

Removing MSI/EXE Packages

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

  1. Click Software Deployment tab.

  2. The list of managed packages , will be displayed.

  3. Click the Actions column next to corresponding package.

  4. Select Delete to remove the package.

The package details will be deleted from the table.