We have several development environments most are still on vSphere 6.5 but one or two have been updated to 6.7.
We have a proprietary management application which monitors the environment. When it finds a VM which is "disconnected" it will register the VMX file to an online host or resource pool.
This has been used for almost a year on VS6.5 without any issues. The nature of our environment and testing means that disconnected VMs are a fairly frequent occurrence.
On VS6.7 however, we notice that occasionally we get a bunch of VMs that don't start up as expected. When examined more closely via a web-client, we find that they are waiting for the "This virtual machine may have been moved or copied" question to be answered.
Does anyone have any ideas or clues as to why we are seeing this in 6.7 but not 6.5?
Is there a way to entice 6.7 into behaving the way as 6.5, or are there fundamental changes we will need to take account of moving forward?
