Hi Folks - https://kb.vmware.com/s/article/1541 talks about keeping the UUID, in our case the application needs it to remain the same, but it has changed and every time it does the app licensing breaks.
We applied the setting to the VM config file uuid.action = "Keep"
However, it testing this out on a test VM and performing a host crash, we now see the VM has a new entry in the config file:
uuid.location = xxxxx and the UUID here has changed.
My assumption here is that this location parameter is just for vCenter \ vSphere and the uuid for the bios will still remain the same so the fix will allow the app licensing to stay functional.
Can anyone confirm this?
could it be that it expects the value to be "keep" instead of "Keep"?
Thanks for pointing this out, this capitalization error is only in this post, but not a mistake in the config file. In the config file it is all lower case. Great eye for detail. 🙂
This is what I have found about UUID:
Within the VMX configuration file the UUID information is stored in three variables: uuid.bios, uuid.location and vc.uuid.
The uuid.location value is what is changing, and our team is wondering whether or not this has any affect on the application that wants to see the uuid.bois, it does appear to remain constant now that the uuid.action = "keep' is set
Normally this shouldn't be a problem, but I am not 100% sure. My recommendation usually is to contact the vendor of the app, as in this day and age of cloud computing this way of licensing etc is not really from this century.