Migrating the Client Automation’s Domain Manager is supported, but the following prerequisites must be strictly followed due to MDB dependencies:
Install Domain Manager - no Microsoft SQL Client Tools installed
Client Automation 14.5 and above
Steps to follow:
1.- On current/old DM server CAF services have to be stopped:
caf stop & caf kill all
hmagent stop
cfsystray stop
camclose
csampmux stop
2.- Take a backup of folder: C:\Program Files (x86)\CA
3-. Export the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\HostUUID
4.- On new server restore the folder: C:\Program Files (x86)\CA
5.- On new server restore the previously exported registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\HostUUID
6.- Create the following string: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\HostUUID\LockHostUUID = 1
For more details, the following article can be reviewed:
Prevent the Host UUID from changing on Virtualized environments
7.- On new DM server, run the CA Client Automation setup and reinstall the Domain Manager and during wizard click Recovery.
The Configure Manager Wizard page opens, select System Replacement and Replacing System options, and specify the location of the DSMRecovery.ini (C:\Program Files (x86)\CA\DSM)
8.- Follow the wizard and start the installation.
9.- If the old Domain Manager had any Cumulative patch installed (CU1, CU2, CU3, CU4, CU5, CU6 or CU7), the solution described in this article has to be applied:
For more details about restoring a Domain Manager installation, the following section of the documentation can be seen: