Quick Post.
I have a customer who provisions a lot of VMs a head of time with generic names. Once the VM is put in use, the name is changed via PowerCLI to reflect what the VM is assigned to. We have been having some problems with our vCenter 6.0u1 which meant we had to restart inventory service (which restarted vCenter) a few times. Each time this occurred, the customer’s VMs would get revert to the original name.
The issue occurred one more time after we upgraded to vCenter 6.0u2, but I couldn’t recreate it after that. Apparently if I RTFM (aka the release notes) I would have known why.
Renaming a VM through PowerCLI or any direct vCenter Server API script, and restarting vCenter Server might revert the VM name to its original value
Renaming a virtual machine through PowerCLI or any direct vCenter Server API script, and restarting vCenter Server might revert the VM name to its original value.
For more information, see KB 2144061.
This issue is resolved in this release.
I have found vCenter 6.0u2 to be a lot more stable, I definitely recommend it over 6.0u1.