When executing Deployment Management (DM), perform the following primary steps of the deployment process:
- From the administrator computer, the infrastructure deployment client component (deployment wizard or dmsweep command) issues a request to the DM manager (DMDeploy) to install an agent on a list of one or more target computers. The deployment manager may be running on a computer that is remote from the client. The list of targets can consist of explicit machine names or IPv4 addresses, or may be obtained from a “container” source such as a Windows domain, an LDAP directory, or a Client Automation query.
For deployment to succeed to each target computer, it is important to ensure that its name, whether entered explicitly or obtained from a container, is suitable for resolving to the address of the target as seen on the deployment manager computer. If, for example, the list of targets retrieved from a directory is not fully qualified with network domain names, deployment may not be able to proceed in certain network configurations.
- A check is made to see if the DMPrimer is already installed on the target computer. If not, DMPrimer will be installed first on the target computer. The DM manager tries to deliver the DMPrimer installation package. The delivery method used depends on the target operating environment and the security that has been enabled on it. After the DMPrimer image is copied across to the target computer, its installation is initiated.
As some operating systems do not have a method for remote invocation of the DMPrimer installation, you may have to establish the installer to be installed on a significant operating system event, such as a reboot. This is termed an asynchronous installation, because the message to indicate completion of the installation is received asynchronously at an unspecified future time. Alternatively, the DMPrimer installation can be performed manually.
- The DMPrimer installer installs itself and the CA Message Queuing (CAM) component on the target computer. During installation, the FIPS mode of the DMPrimer on the target computer depends on the FIPS mode of the manager. The manager passes the FIPS mode as an installation parameter. This parameter is also updated in the dmprimer.cfg file, which is part of the DMprimer installation.
However, on start, DMPrimer reads the FIPS mode from the agent configuration policy on the target computer. If successful, the primer updates the dmprimer.cfg file with the FIPS mode of the agent and initializes in that mode. If there are no agents installed on the target, the DMPrimer initializes in the mode specified in the dmprimer.cfg file.
Note: On most operating systems, the DMPrimer installation needs to run with elevated privileges.
- Once the DMPrimer is installed and DMDeploy has received the "installation complete" signal from the target computer, package deployment can be initiated. A DMDeploy manager that has previously installed a DMPrimer and has authenticated with it can deploy packages without needing to resupply user names or passwords. This is done through authentication using public and private keys. You can force the deployment manager to retransfer and install the DMPrimer even if a version is already present. To do so, set the "AlwaysDeployPrimer" configuration policy using the DSM Explorer.
For details on using the deployment manager through the DSM Explorer, see the online help for Deployment wizard.
