The MSI installation packages support a command line interface. This can be used when deploying DSM functionality to remote systems through alternative methods, such as custom built DVD or CD, or when building Client Automation functionality into host deployment images.
The Microsoft Windows Installer (MSI) installs software from package files which have the file extension of .msi.
Msiexec.exe is the executable command which can be used to install MSI packages from the command line. Msiexec is a very flexible tool with many command line options. You can find the detailed descriptions of the msiexec options and parameters in the Microsoft Online Help.
All MSI packages support general options. As well, some MSI packages support package specific options. These two sets of options can be used to control the exact manner in which a specific application is installed.
An example of an msiexec command using general options (/i, -l*v, /qn) and the Manager package specific installation option ADDLOCAL is the following:
msiexec /i "x:\WindowsProductFiles_x86\Manager\Manager.msi" -l*v "c:\DSMSetupMgr.log" ADDLOCAL=Manager,MgrDC,MgrAM ALLUSERS=1 /qn
The general options and package specific options are described under "General Options for msiexec" and "Package specific MSI Properties".
Note: Agent package specific options are those installation parameters used during interactive deployment to specify the "additional Windows install options" on the Agent Configuration page of the Deployment wizard. On that page, you can enter multiple install options, separated by spaces, in order to override existing options.
Important! If you are installing DSM components directly using the MSI command line msiexec, you should always set the MSI installation property ALLUSERS to the value 1 (meaning: “Installs for all users but the user requires administrative access privileges on the computer”) to allow later upgrade, uninstall, or re-install through Software Delivery or Deployment functionality out of a DSM manager. If you do not set the parameter like this or leave it empty, the component is registered for the particular user installing it at the first time and cannot be maintained by using manager functions.
Note on specifying system names:
Whenever the Client Automation Installer asks for a system name to be entered, we strongly recommend that you enter a fully qualified domain name (FQDN) including domain suffix, so that computer systems in other network domains can be reached even if request forward is not configured for all DNS involved.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|