Client Automation - How to Include the DSM Agent in a cloned OS Image
search cancel

Client Automation - How to Include the DSM Agent in a cloned OS Image

book

Article ID: 9466

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

If the chosen method of deploying the DSM Agent to other computers is an imaging tool like ImageX, or an image file of a virtual machine using a tool like VMWare, some actions are required on the template machine if the Client Automation's Agent is part of the image.

Environment

Client Automation - All Versions.

Resolution

Important: This article contains information about modifying the registry. Before you modify the registry, make sure to create a back up of the registry and ensure that you understand how to restore the registry if a problem may occur. For more information about how to back up, restore and edit the registry, please view the relevant Microsoft Knowledge Base articles on support.microsoft.com.

ITCM 12.x, 14.x:

Before generating the image, perform the following actions on the template machine:

  • Start the agent and register it with a manager to ensure proper verification of the management server information.
  • Run the following commands:

    caf stop
    ccnfcmda -cmd DeleteParameter -ps itrm/rc/host/managed -pn convertedhostuid
    ccnfcmda -cmd DeleteParameter -ps itrm/cfencrypt -pn LOCALID
    ccnfcmda -cmd DeleteParamSection -ps itrm/rc/security/providers/common/users
  • Delete the HostUUID key from the registry:

    On a 32-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\HostUUID
    On a 64-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\HostUUID
    On UNIX/Linux: Delete the file /etc/cadmuuid
  • Generate the image to be deployed BEFORE starting the DSM agent again.


All Versions

The deleted values 'convertedhostuid', 'LOCALID' and 'HostUUID' are machine-specific and will be properly regenerated on the template machine, as well as on the target machines at agent start.

The default users for the security providers will not be recreated automatically by the host. Therefore, if the security mode of the host is not set to centralized security, the following command to re-create the default users for the host must be executed on the template machine, as well as on each target machine:

rcUtilCmd.exe CreateDefaultUsers

Note: 'rcUtilCmd.exe' can be found in the ......\Program Files\CA\DSM\bin folder