How to Fix WMI issues automatically

While Ago I have posted a solution on how to fix WMI(Windows Management Instrumentation) issues using simple batch script that stops WMI service and recompile all MOF files etc. http://eskonr.com/2009/03/how-to-troubleshoot-the-systems-which-has-wmi-issues-rebuild-wmi-repository/

While working with new windows 7 migration project, we had lot of computers with wmi issue but how to identify which has wmi and fix it automatically. There could be various reasons if configmgr client is not reporting to site server but wmi issue one of major problem .if wmi issue occur, nothing can be performed on configmgr client. No policies, no inventory information nothing will be received or sent to MP.

It would be difficult to identify machines which as WMI corruption so either you can apply wmi script Via GPO to run every time when computer boots up else go with psexec to run the script remotely or different methods which you would prefer.

I come up with simple script that check the functionality of WMI if WMI is working fine, exit the script else repair WMI functionality.

This script you can apply through Logon or make it on schedule basis to run every twice or run once a day through Task Scheduler job on all the machines http://msdn.microsoft.com/en-us/library/windows/desktop/aa383614(v=vs.85).aspx

WMI Isn't Working! ? http://technet.microsoft.com/en-us/library/ff406382.aspx

Here is out Batch script that check the functionality of wmi using simple wmic command:

wmic computersystem get name

if the the above command gives any output,script exit else repair it.

Here is the complete Batch script :

REM Check if WMI is functioning correctly or not

REM Get computername from WMI

wmic computersystem get name

IF %ERRORLEVEL% EQU 0 goto success

:failure

net stop ccmexec /y

net stop VMAuthdService /y

net stop winmgmt /y

c:

cd %systemroot%\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

net start winmgmt

net start VMAuthdService

net start ccmexec

goto end

:success

goto end

:end

Some theory about WMI and how to check if it is working or not.

What is WMI (windows management Instrumentation)?

Windows Management Instrumentation (WMI) is the infrastructure for management data and operations on Windows-based operating systems

WMI can be used in all Windows-based applications, and is most useful in enterprise applications and administrative scripts

For example, you can:

· Start a process on a remote computer.

· Schedule a process to run at specific times on specific days.

· Reboot a computer remotely.

· Get a list of applications installed on a local or remote computer.

· Query the Windows event logs on a local or remote computer.

How to connect to WMI (local or remote computer):

Type wbemtest from Run command

clip_image001

clip_image002

Click on Connect

clip_image003

The Default Name space is root\cimV2 .You have many namespaces available in WMI.

Click on Connect

clip_image004

Click on Enum Classes

clip_image005

Select Recursive

clip_image006

You can see lot of classes available for cimV2 name space. For more information about available classes in WMI namespace called cimV2 ,please look at here http://msdn.microsoft.com/en-us/library/windows/desktop/aa394084(v=vs.85).aspx with its description and objects within it.

Now you can see all the classes available within cimV2 name space.

To know more about what each class contains and its objects with in it

Double click on any class which you want to look at it and click on name which you desire

clip_image007

Now we will see how to execute to get required information with in WMI:

Go back to namespace called cimV2 shown below :

clip_image008

Click on Query:

clip_image009

Click on apply to see the results. You can execute any query which has correct syntax to get the correct information.

How do you run wbemtest on remote computer?

1. To connect remotely using tools like CIM Studio or Wbemtest, you must specify a namespace in the form "\\<machinename>\root\<namespace>"
For example: \\mymachine\root\cimv2 as shown below and perform the steps whatever you need as did above.

2. clip_image010

How do you check remotely if WMI is working well or not ?

You do it via wbemtest or wmimgmt.msc from run command

clip_image011

clip_image012

clip_image013

clip_image015

 

clip_image017

clip_image018

See the error above. The RPC server is unavailable means something wrong with the computer could be machine doesn’t not exist on the network or name resolution or permission issue etc

If computer is connect successfully and if you look at properties of the computer ,you will see the below screen,

clip_image019

For more information about WMI Faqs ,please refer this guide http://technet.microsoft.com/en-us/library/ee692772.aspx

Reference Guides on WMI troubleshooting: http://eskonr.com/2009/03/how-to-troubleshoot-the-systems-which-has-wmi-issues-rebuild-wmi-repository/

http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx

Reference http://social.technet.microsoft.com/Forums/en-US/configmgradminconsole/thread/a9922b7f-3b81-4b2b-866a-423106b0e9fe

Feel Free to post your comments.

19 Responses to "How to Fix WMI issues automatically"

    1. Hi Charles,
      if you have WMI issues, client will not be able to download policies from SCCM and you cannot deploy anything due to WMI issue.
      If the client is able to receive the policies etc ,you will have No or less issues on WMI.

      Thanks,
      Eswar

      Reply
  1. Wont this only let you know when win32_ComputerSystem in the CIMV2 space is bad. It seems you could have corruption in other name spaces and still get successful results back. Or is this the only namespace that really matters to SCCM and thus why you only test that space.
    I guess one could put as many tests before the rebuild which test for failure and if at least 1 fails, then rebuild.

    Reply
    1. If WMI is not working,then it would be issue with name space but not the with class like win32_computersystem.I don't see any scenarios like win32_computersystem class working but other classes(like win32_opearatingsystem) has issues while retrieving information.
      did you see any such scenarios ? CIMV2 is the namespace used to retrieve the Client info to CM database.

      Reply
  2. Amazing Stuff Eswar..!!!! Your script saved my lots of time and logging case with PSS. I was working on repairing WMI for more 24 hours but it was failing. Your script worked like charm and all my issues got resolved.

    Once again Thank You so much for making and providing this script.

    Reply
  3. I have set the batch to @echo off at the top, and we're seeing the black command prompt box mentioned (by Bhaskar) open on our end (with the name of the computer shown)

    Sending out via PSEXEC isn't working to the systems with problems due to WMI and RPC not functioning properly.

    Reply
    1. yes,if you try to run on local computers,you will get prompt displaying the progress of the script .Over remote computers,i dont see any prompt.,prompt only shows on local machine from where you run but not remote.
      If you have issues connecting to remote computers,you will have to check if you have access to wmi/fix RPC errors.
      for RPC error,i usually check if name resolution is correct or not.Sometimes same IP address is assigned to multiple computers(2).so check that and fix the errors before you try to connect to wmi.

      Reply

Leave a Reply