sms: addressing wmi corruption...

i picked up this tidbit from jeff gilbert on the sms mailing list. anyway, there are a few ways to address this if the os of the affect client is windows xp or windows 2003 or greater. here's what he had to say on the matter:

There is help for XP SP1-SP2 and Server 2003, SP1 systems to diagnose and repair WMI corruption: To check the WMI repository for errors on a Server 2003 SP1 system, run the following command from command prompt:

• rundll32 wbemupgd, CheckWMISetup

Once you've run that command, check the setup.log file located at: %windir%\System32\Wbem\Logs\Setup.log. Check for entries from today's date. If you find none, then WMI is probably OK and you should continue troubleshooting somewhere else. If however, you see an error message from today saying that it can't find a namespace then yes, your WMI repository does have issues and you should do the below:

• rundll32 wbemupgd, RepairWMISetup

This will re-create your WMI repository minus any custom .mof additions that were implemented without the -autorecover switch. For Windows XP SP2, use the following command to check for corruption, and repair if necessary:

• rundll32 wbemgupgd, UpgradeRepository

For Windows XP SP1, the check and repair commands are below and function just like the Windows Server 2003, SP1 commands:

• rundll32 wbemupgd, CheckWMISetup
• rundll32 wbemupgd, RepairWMISetup

These are the commands I personally use to try to troubleshoot WMI corruptions. Hopefully they can help you too. Remember to always check that setup.log (%windir%\System32\Wbem\Logs\Setup.log) to see what is going on, and remember that any mof additions compiled without the -autorecover switch will be lost whenever you rebuild your WMI repository!

just keep in mind... the commands above do have a space after the comma. it IS required.