{"id":8756,"date":"2007-01-26T07:45:00","date_gmt":"1999-11-29T20:00:00","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=8756"},"modified":"2007-01-26T07:45:00","modified_gmt":"1999-11-29T20:00:00","slug":"wmi-diagnosis-utility-v2-0","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=8756","title":{"rendered":"WMI Diagnosis Utility V2.0"},"content":{"rendered":"

This one might be useful to MOM 2005 administrators who are often the first to find and be plagued by WMI failures.\u00a0 Microsoft has released<\/a> version 2 of a WMI diagnosis utility.\u00a0 It’s actually a VBS script that’ll test your WMI service.\u00a0 The download includes the script and documentation.\u00a0 I’ll be using this puppy myself today.\n<\/p>\n

EDIT: Updated 26\/01\/2007 @ 14:10<\/em>\n<\/p>\n

My client has been having massive RPC\/WMI issues which is breaking MOM 2005.\u00a0\u00a0I suspected that the engineering team has "hardened" the network some time during the initial MOM deployment.\u00a0 After that, they been seeing thousands of WMI alerts every day plus agent management\/deployment was broken (RPC).\u00a0 All the usual suspects (naming, firewall, IPSEC) were quickly ruled out.\n<\/p>\n

I downloaded the WMIDiag.vbs script and ran it on a sample server.\u00a0 It stores 3 files in the %TEMP% folder, including a .TXT file.\u00a0 The .TXT file is a summary of the tests.\u00a0 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.\n<\/p>\n

A big "Thank you" to the authors of this utility.\n<\/p>\n

BTW, you can make some advanced use of this script:<\/p>\n