This one might be useful to MOM 2005 administrators who are often the first to find and be plagued by WMI failures. Microsoft has released version 2 of a WMI diagnosis utility. It’s actually a VBS script that’ll test your WMI service. The download includes the script and documentation. I’ll be using this puppy myself today.
EDIT: Updated 26/01/2007 @ 14:10
My client has been having massive RPC/WMI issues which is breaking MOM 2005. I suspected that the engineering team has "hardened" the network some time during the initial MOM deployment. After that, they been seeing thousands of WMI alerts every day plus agent management/deployment was broken (RPC). All the usual suspects (naming, firewall, IPSEC) were quickly ruled out.
I downloaded the WMIDiag.vbs script and ran it on a sample server. It stores 3 files in the %TEMP% folder, including a .TXT file. The .TXT file is a summary of the tests. Sure enough, it screamed that expected configurations relating to BUILTINNETWORK SERVICE (the user that the MOM Agent runs as) and BUILTINPERFORMANCE LOG USERS were not found and that this could break WMI client applications.
A big "Thank you" to the authors of this utility.
BTW, you can make some advanced use of this script:
- MOM: Make a custom management pack. Set up a timed rule that runs the script as a response. Use a 3rd party log parsing utility to scan the log file for errors.
- SMS 2003: Deploy the script and run it on a recurring basis (the same way the Inventory tools do). Gather the log file using SMS file collection for later analysis or monitor the log file using MOM 2005 and a 3rd party log parsing tool.