This is VM at the hosting data center facility. Using remote hands.
Windows 2008 Svr hang and vCenter lost information about the VM and cannot vMotion it.
The only option they have without waiting for VMware support is to hard reset the host. As this is a shared ESX environment they'd be looking at multiple VM's across multiple platforms having the rug pulled out from underneath them.
As the host is currently headless due to the lack of vCenter connectivity the VM will not vMotion over to an available host because the vCenter has no information on the health of the server and hence cannot make a decision to bring it online on an alternative host.
The potential for damage is too high for us to risk taking so many servers offline, so they elected to escalate it to VMware under the highest possibe priority their support contract with them would allow.
What other methods can be explored at this point. Does it have to be done via the vCenter only??