Thoughts from the EPS Windows Server Performance Team
Useful Microsoft Blogs
CAN'T CONNECT TO REMOTE WMI
Description: WMI can fail for a number of reasons. 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.
If WMI returns error messages, be aware that they may not indicate problems in the WMI service or in WMI providers. Failures can originate in other parts of the operating system and emerge as errors through WMI. Never delete the WMI repository as a first troubleshooting step because deleting the repository can cause damage to the system or to installed applications.
Scoping the Issue: When dealing with troubleshooting remote WMI connectivity, we need to first ensure that the local WMI subsystem is healthy. The quickest way to do this is via the WMI Control snap-in. Please refer to the WMI Permissions and General Errors 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.
When working on WMI issues, we also need to check the status of DCOM. If you are not terribly familiar with DCOM, our blog post "COM and DCOM for Administrators" is a good place to get familiar with the basics. Changes to default COM security may result in problems and unexpected results. We can use DCOMCNFG to view and change settings as needed
You can add the Administrators group and grant the group Local and Remote access if it is not already present.
Under the Default Launch and Activation Permissions, ensure that at least INTERACTIVE, SYSTEM and Administrators are set to Allow Launch locally and remotely.
Data Gathering: In all instances, collecting either MPS Reports with the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done. Additional data required may include the following:
Troubleshooting / Resolution: Once you have gathered the data, here are some things to check:
How do you change WMI permissions on hundreds of machines? Is there a command line method? Running the MMC is not a viable option.
WMIDiag 2.1 is now available!
Supported Operating Systems: Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP
I post a comment here, however it didn't see it. Not sure why. This time I will make it simple. Just wonder if you could take a look at my post on forum social.msdn.microsoft.com/.../4161d6a1-1b52-4aa9-98b9-eacad5ba2a90. I have a weird issue for remote wmi.