I've referred below articles in order to determine how to prevent this issue. According to those articles, the VM property value named "instanceUUID" is the easiest way to uniquely identify a VM in globally. I also checked those instanceUUID values in VM's which are reported duplicate bios.UUID. Even though bios.UUID's duplicated instanceUUID was not duplicated. But I did not find any KB, article or forum related to feeding the data to a CMDB system using instanceUUID values.
Uniquely Identifying Virtual Machines in vSphere and vCloud Part 1: Overview
https://blogs.vmware.com/vsphere/2012/02/uniquely-identifying-virtual-machines-in-vsphere-and-vcloud...
Uniquely Identifying Virtual Machines in vSphere and vCloud Part 2: Technical
https://blogs.vmware.com/vsphere/2012/02/uniquely-identifying-virtual-machines-in-vsphere-and-vcloud...
In 2017 he wrote an update to address cross vCenter vMotion:
Uniquely identifying VMs in vSphere Part 3: Enhanced Linked Mode & Cross VC-vMotion
https://www.virtuallyghetto.com/2017/07/uniquely-identifying-vms-in-vsphere-part-3-enhanced-linked-m...
Can anyone please advise us how can we pull those instanceUUID details via vCenter? Is there any other method to extract instanceUUID details from guest OS level? Or any other ways rather than PowerShell.?
