Previous Topic: Troubleshooting the Errors ReportedNext Topic: vDisk Record Is Not Found in the DSM Explorer

Diagnostics and Troubleshooting › No New Host UUID for Microsoft Hyper-V Clone

No New Host UUID for Microsoft Hyper-V Clone

When using VM to VM cloning in Microsoft Hyper-V, it is not possible for the DSM agent to identify that it has been cloned. Therefore, it cannot generate a new host UUID. The reason is that the UUID source is Microsoft Windows Management Instrumentation (WMI) and not BIOS, the default source for Client Automation. For Microsoft Hyper-V, the UUID is accessible only from the hypervisor WMI and not the guest.

Note: This problem does not occur when cloning from a template.

To ensure that the clones are represented as new virtual machines, follow these steps:

  1. Stop CAF.
  2. Delete the HOSTUUID key from the registry: HKLM\SOFTWARE\ComputerAssociates\HostUUID
  3. Change the host name and reboot.

Asset Management does not Collect Inventory Data on VM of Citrix XenServer

The Asset Management agent does not collect inventory data for the following subinventory nodes when the agent runs on a virtual machine of Citrix XenServer: