Microsoft has a nice Utility, WMIDiag v 2.0 releaseed 1/25/2007
http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx
http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx
This tool helps you run reports to determine erorrs with WMI on your machine.
"This document (developed in conjunction with the WMI team at Microsoft) is designed to help you troubleshoot problems with WMI scripts and the WMI service. Although the focus here is on scripting, the same troubleshooting information can be applied to other WMI consumers, such as Systems Management Server (SMS). Scenarios – and the error codes they produce – will often be the same regardless of whether you encounter problems using a script, the WMIC command line, a compiled application (such as SMS) that calls WMI, etc."
WMI fixes can still be used:
Windows XP
rundll32 wbemupgd, UpgradeRepository
Windows 2003
rundll32 wbemupgd, RepairWMISetup
A sample of the report is listed below:
DCOM Status: ................................ OK.
WMI registry setup: ............................ OK.
WMI Service has no dependents: ................. OK.
RPCSS service: ................................. OK (Already started).
WINMGMT service: ............................... OK (Already started).
--------------------------
WMI service DCOM setup: ........................ OK.
WMI components DCOM registrations: ............. OK.
WMI ProgID registrations: ...................... OK.
WMI provider DCOM registrations: ............... OK.
WMI provider CIM registrations: ................ OK.
WMI provider CLSIDs: ........................... OK.
WMI providers EXE/DLL availability: ............ OK.
If you are having problem with WMI connection or errors check this out. Running on your SMS server might just find a an error or security setting that you need to change.
