How to include the CA Client Automation Agent in an OS image
Document ID :
Last Modified Date :
Show Technical Document Details
CA Client Automation
CA Client Automation:Release:12.5
CA Client Automation:Release:12.8
CA Client Automation:Release:12.9
CA Client Automation:Release:14.0
CA Client Automation:Release:1401
CA Client Automation:Release:1402
DESKTOP AND SERVER MANAGEMENT:DTSVMG
CA Client Automation:BITCM
CA Remote Control:TNGRCO
CA Software Delivery:TNGSDO
CA Asset Management:TNGAMO
How to include the CA Client Automation Agent in an OS Image?
All versions of CA Client Automation
This article contains information about modifying the registry.
Before you modify the registry, make sure to create a backup of the registry and ensure that you
understand how to restore the registry if a problem may occur.
For more information about how to backup, restore and edit the registry,
please view the relevant Microsoft Knowledge Base articles on
Following are the steps to include the CA Client Automation Agent in a Ghost Image:
- Before running Sysprep and creating a ghost image, install the CA Client Automation Agent on the Machine
- Run the following commands:
a) caf stop
b) ccnfcmda -cmd DeleteParameter -ps itrm/rc/host/managed -pn convertedhostuid
c) ccnfcmda -cmd DeleteParameter -ps itrm/cfencrypt -pn LOCALID
d) ccnfcmda -cmd DeleteParamSection -ps itrm/rc/security/providers/common/users
e) caf start
Some of these commands may fail with parameter doesn't exist errors.
This is expected and would not cause any issues.
- Delete the HostUUID registry key:
On a 32-bit OS:
On a 64-bit OS:
- For Remote Control Agent run:
Once the above steps are performed, you can Sysprep the machine and create a ghost image.
Please note that CA Strongly recommends using the Deployment Wizard to deploy the Agents on the target machines.
Though these steps would help in integrating the agents as part of the Ghost Image,
CA does not guarantee proper functionality of the agent as designed.
Was this information helpful?