I’ve seen this happen a few times now, while looking at your Virtual infrastructure, one or more client machines is greyed out and shown as (Orphaned).
Solution
If you have many guests VM’s on one host with this problem, you can cure this by removing the parent host and re-adding it to the cluster, then right clicking it and select “Reconfigure for HA“.
Or you can do the following, on a machine by machine basis.
1. Right click the affected VM and select “Remove from Inventory” (nothing gets deleted don’t worry.)
2. Select one of your ESX hosts > Configuration > storage > Right click the storage that holds the virtual machine we are dealing with and select “Browse Datastore” > Locate the machines .vmx file > Right click > Add to inventory > Follow the instructions.
Related Articles, References, Credits, or External Links
At time of writing (30/09/10) it seems I cant get a definitive answer! My colleague tried to log a third line support call with Microsoft this week, as soon as they found out that Exchange 2010 was running in a VMware environment, they (literally) hung up on him.
Quote ” Products that have passed the SVVP requirements for Windows Server 2008 R2 are considered supported on Windows Server 2008 and Windows Server 2003 SP2 and later Service Packs, both x86 (32-bit), and x64 (64-bit).”
And The platform it was running on IS listed (ESXi 4.0 U1).
When presented with this evidence the response was “We will try and fix it on a “Best Endeavour” basis” and the problem (which had nothing to do with VMware, it was actually Microsoft Threat Management Gateway that caused the problem!) was resolved.
Sorry Microsoft that is just not good enough! My company pay handsomely for their gold partnership status, and we expect to get third line support on the products we sell. The product is either supported or it is NOT, don’t publish that it is, then use the fact that is running on third party virtualisation to get the problem off your support call queue. Because somewhere there is an Engineer/Consultant who has persuaded THEIR client to part with money to buy YOUR product.
I openly invite Microsoft – Third Line Exchange Support, The Exchange Development team and anyone else to respond to me. I will publish any pertinent response.
Related Articles, References, Credits, or External Links
