Hello, We use an internally built inventory and asset management solution.
We are facing the following issue : How to identify uniquely a computer, knowing that it can be a VM and that a VM may have been duplicated ?
Let me clarify : a VM that is imported in Hyper-V, may have ALL the usual IDs you can access from the guest identical to another VM :
That is : same UUID, same MAC address, same SID, same BIOS ID, same Netbios name. Of course, the won't be able to function well in the same domain/forest unless properly isolated and this usually is not something you want to have in a production environment.
But let's face it, it may happen and if it is all you have as a primary key used to differentiate machines in a relational database, then you're screwed.
So i thought that the best way would be to access the VM GUID (the one of the XML VM files) and add it to build the primary key.
It is no problem using WMI and Msvm_KvpExchangeComponent from the host, but it would be nice to have access to this data through the guest, meaning that the KVP should be exposed on the guest too through the integration components.
Feel free to discuss, i think it is an important issue.