I had some funny WMI problems yesterday. I couldn’t connect to any WMI namespace except to root. This means, the WMI service was running and had no errors. The root cause of the problem was the SCCM Eval Task, which is running on any SCCM Client in combination with Windows Management Framework 3.0.
To repair WMI problems, I used these commands in a batch file:
sc config Winmgmt start= disabled sc stop Winmgmt cd /d %windir%\sysWOW64\wbem for %%i in (*.dll) do RegSvr32 -s %%i cd /d %windir%\system32\wbem for %%i in (*.dll) do RegSvr32 -s %%i sc config Winmgmt start= auto sc start Winmgmt cd /d %windir%\system32\wbem for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s cd /d %windir%\sysWOW64\wbem for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s REM If you are using wmi with fixed port you have to set it again "winmgmt /standalonehost" REM Reboot Computer and check again!!!
The key part was to reregister the mof files with the following command in the wbem directory:
for /f %%s in (‘dir /s /b *.mof *.mfl’) do mofcomp %%s
I hope these commands will help you too.
Latest posts by Thomas Kurth (see all)
- Office 365 DLP – Add detection of the swiss social id to detect personal data - February 8, 2019
- Take action: Default permissions in the Microsoft Compliance Manager gives all users full access - February 2, 2019
- Test connectivity to various Azure and O365 services - January 9, 2019