VMware Note

1) A VMware High Availability host failure has occurred.
2) The virtual machine was unregistered directly on the host.
3) The ESXi host is disconnected.
4) The user does not have privilege to access the virtual machine.

A virtual machine can show up as invalid or orphaned in these situations. To resolve these issues, see the troubleshooting steps provided for each situation:
•After a vMotion or VMware DRS migration
•After a VMware HA host failure occurs, or after the ESX host comes out of maintenance mode
•A virtual machine is deleted outside of vCenter Server
•vCenter Server is restarted while a migration is in progress
•Too many virtual machines are scheduled to be relocated at the same time
•Attempting to delete virtual machines when an ESX/ESXi host local disk (particularly the root partition) has become full
•Rebooting the host within 1 hour of moving or powering on virtual machines
•A .vmx file contains special characters or incomplete line item entries
•Reload all invalid virtual machines on a single host at one time