WMI issues in VMware based Machine Windows 2008 R2 Servers affecting SCCM Clients

Question

Dear
Brothers,<o:p></o:p>
I came to
an observation particularly in dealing with Windows 2008R2 Servers Vmware Based
Virtual Machines with SCCM Clients.<o:p></o:p>
Observation:<o:p></o:p>
1. Windows
2008R2 Virtual Machine with Vmware Tools installed (Also depending in the
entries of WMI, I supposed). <o:p></o:p>
When the SCCM Server Pushes the client on this Servers, I found out that the SCCM Client
seems to be installed perfectly but when I tried to perform a remote WMI Query
and the response is displayed below (The RPC Server is unavailable).<o:p></o:p>
Now, I know that this kind of issues is something to do about DCOM Configuration
for Remote Access right?
Well, sad to say the settings has been checked, trippled checked actually to make sure it is correct with the correct permissions required and proven correct up to the last settings.
I even compare the settings to those in some Windows Servers with Working WMI Remote Access.
=========
What I have observed is that when we make a VMware Systems and install the
VMware Tools (see picture below) first before installing the
SCCM Client and the issue regarding WMI Remote access issues happens (The RPC Server is unavailable).
I proved it by creating a new VM Machine, then conduct installation in this order
SCCM Client first and then the
VMware Tools by this way so far the WMI Remote access works perfectly.
Now the Question:
Since we have atleast 70 VM Servers in production with this issue, and I proven that the VMware Tools is something to do with this issue, somehow now I need to resolved this in a logical manner.
For some of us who can guide me to resolved the issue without uninstalling the VMware Tools and fixing the WMI settings and let the SCCM Client work.
Regards,

Answer 1

We also have this issue. Nearly all of our terminal servers. I have to run a script to fix the issue and then reboot. It works, but only for a few days and then it starts all over again...
::to fix "not found" wmi error
::to fix .net calls to wmi repository
::to fix "initialization failure" error
net stop winmgmt
c:
cd c:\windows\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
mofcomp exwmi.mof
mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
mofcomp exmgmt.mof
For the Update on this case Microsoft didn't find out direct connection of WMI issue to any contributors, however the clients
from Microsoft and and 3rd party application such as VMware is highly dependent on WMI for its total function.
Things that we have learned:
1. Your script is the primary solution as recommended as well by Microsoft, but this is to restore the WMI to its healthy State.
Is the error gone?
no definitely not.
   Note: The WMIDiagnostic tool does not help to isolate at all, not even Microsoft is validating the credibility of its generated Logs from this tool.
2. You need to apply the Hotfixes recommended by Microsoft to eliminate the WMI repository to increase its capacity which contributes to the Service to stall. Deliver the Patches via SCCM or any means of your patch deployment.
3. Don't forget to reboot the Affected Server every Hotfix installation, this seems fix the issue. For 3 months now the usual system who got the WMI issue most of the time is no longer encountering the WMI errors. So far this is the solution, what causes
the issue? according to Microsoft the cause is the absence of the patches.