Client Automation - Virtualization of Domain Manager
search cancel

Client Automation - Virtualization of Domain Manager


Article ID: 9386


Updated On:


CA Client Automation - IT Client Manager CA Client Automation


Virtualization of a Client Automation's Domain Manager often results in servers getting a new MAC address and HostUUID.

What impact does this have on the environment and how can it be minimized?


Client Automation - All Versions


Logic dictates that if the System UUID, MAC address and Disk Serial Number change, a new HostUUID is created, for more information about HostUUID, the following article can be reviewed:

Client Automation - Everything you need to know about the HostUUID and computer uniqueness

If the MAC address and the HostUUID change, you will end up with 2 domain managers having the same name within the DSM Explorer. You would have to remove the physical one from All Computers as well as from Control Panel/ Scalability Servers/All Scalability Servers.

Because the HostUUID changes, all SD deployed software would be removed.

In order to prevent this, you should -temporarily- disable RAC from configuration policy: Set following Policy to FALSE:

DSM > Software Delivery > Manager > RAC:Policy

Do not start the virtualization process until a configuration report shows that this modification is applied.

Another, easier, way to prevent the HostUUID from changing, is by setting registry attribute 'LockHostUUID' to 1 before starting virtualization. This value can be found in the registry key:


or, on 64bit systems:


This is particularly useful if the source Domain Manager will no longer be part of your ITCM environment.

The VMWare P2V process has the ability to keep the original MAC Address. You should consider this unless the original physical machine is to remain in the network, in which case it should have ITCM removed after the virtualization process and before bringing it onto the network again.

If Domain Managers report to an Enterprise Server, it is recommended to unlink them prior to virtualization and relink them afterwards.

Once virtualization is done, test if everything works fine, especially the System Engine (with all of its assigned tasks) and System Delivery Engine.

After virtualization, the ca_manager table within the MDB may contain rows for both old and new Domain Manager, the old one should be removed.