I have a suspicion you have "dual" membership on this host, and have already registered it to a New vcenter. If that is the case you need to remove it from the New vcenter to Complete the removal from the old vcenter.
I've removed the host from the new vCenter server, rebooted the host and old vCenter server and reconnected the host back to the old vCenter server and still seeing the orphaned VMs. I was able to remove most of them following this KB, but sure enough theres one that just wont remove. In fact when I try to remove it it actually crashes my vCenter connection.
Also, not sure if it matters, but this orphaned VM only shows up in vCenter Server for this host. It does not show up when connecting to the host using the vCenter client directly. Ive also made sure there are no rogue files on this hosts datastore.
Any suggestions on how to remove this stubborn orphaned VM?
Im heading out for vacation for 2 weeks starting tomorrow so I may not reply until I return.
There are two concerns
1. Removal of Host from old VC
2. Existence of Orphaned VM
let's start with Host
1. remove it from rest of other VCs
2. put it in maintenance mode.
3. reboot and add
Orphaned VM :
1. If VM still exist on Host, check if it really belongs to host. locate .vmx and add back to inventory then remove.
2. If VM doesn't exist on host ,check if this host holding lock of any .vmdk of this VM.