![]() ![]() " is a good place to get familiar with the basics. If you are not terribly familiar with DCOM, our blog post " When working on WMI issues, we also need to check the status of DCOM. ![]() If it shows any errors or is unable to display the information, document the message seen (or capture a screenshot) On the General tab, you should see information about the operating system and the version of WMI. If the WMI service is configured correctly, the WMI Control will connect to WMI and display the Properties dialog box. Right-click WMI Control (Local), and then click Properties. Topic on the AskPerf Support Center for testing and ensuring that WMI is working locally on each box as well as data collection before moving to troubleshooting remote connectivity.Ĭlick Start, click Run, type wmimgmt.msc, and then click OK. The quickest way to do this is via the WMI Control snap-in. When dealing with troubleshooting remote WMI connectivity, we need to first ensure that the local WMI subsystem is healthy. Never delete the WMI repository as a first troubleshooting step because deleting the repository can cause damage to the system or to installed applications. Failures can originate in other parts of the operating system and emerge as errors through WMI. If WMI returns error messages, be aware that they may not indicate problems in the WMI service or in WMI providers. Some of those can include not having appropriate rights and permissions for access to machines or namespaces, problems with provider registration, corrupted repository, and scripting errors to name a few. ![]() First published on TECHNET on Apr 13, 2009 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |