Microsoft utility helps admins diagnose WMI services

Windows Management Instrumentation (WMI) is a subsystem in Windows that lets you programmatically access a good deal of information about the system or running applications. But WMI is a fairly esoteric system, and from the outside, it's hard to determine if it's running correctly. If something goes wrong with WMI, the symptoms can be hard to trace; what may look like a problem in another part of the system entirely may in fact be a WMI problem.

Microsoft created its WMI Diagnosis Utility to help an experienced administrator learn about possible problems in a system's WMI setup. It consists of a VBScript program and a collection of data files in Excel spreadsheet format, which the admin can use to check the WMI namespaces in the system he is scanning against the expected results.

When you run the script, it checks every possible namespace that it has data for and logs the results to a very long and detailed results file. For this reason, the tool really isn't for use by anyone except experts who know how to interpret the results.

However, whenever it logs an error (look for the string !!ERROR in the log), it will suggest a fix for any problems it encounters (assuming one is available). The most critical errors that indicate a functional problem with WMI will be logged prominently and will return a "Fail" code. Less critical errors will be logged but without causing the entire analysis to be logged as a failure.

There are a few ways to cut through the

    Requires Free Membership to View

thicket of data that the script returns and get the most relevant bits of information. For instance, if you only want to scan a given namespace, you can pass the basenamespace parameter to the script. This limits the script's scanning to the namespace in question and will speed things up if you know you're experiencing problems with a given namespace. More details on how to narrow the scope of the scan or find more precise results are listed in the script's documentation. Which, as you might guess, is extremely detailed..

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators.

More information from SearchWinSystems.com

This was first published in April 2006

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.