I need to enable the WMI remote access in a lot of client machines in order to connect to these machines and get some information. These machines have installed different versions of windows (Windows XP, Windows 7, Windows Server 2003). I followed the steps described in these articles and it works ok in some cases (the WMI remote access is enabled) but sometimes is just impossible. :(

My question is: Where can I find something like a check list of steps or a step-by-step guide to enable WMI remote access in any Windows machine?


  1. Always I use administrator accounts to access the remote machines
  2. The most common error which is reported is, Access Denied (decimal -2147024891 or hex 0x80070005). I know which is related to DCOM security settings. so I set the proper remote access to the Administrator accounts in the WMI and DCOM services.
  3. I tried disabling the Firewall without luck.


I found the solution ¡¡¡, all the client machines which has problems, have the same GPO configuration which makes to the remote logons are being coerced to the guest account, to fix that using the Local Security Policy editor (secpol.msc) you must Select Network access: Sharing and security model for local accounts. and set the value to Classic - local users authenticate as themselves.


  • You should post your solution as an answer and mark it as the solution so that this won't appear as an open question.
    – gWaldo
    Commented Sep 24, 2011 at 0:51

1 Answer 1


Just FYI, you posted the same link twice.

Which machines work, and which don't? Is there a difference depending on the OS?

What error message(s) are you getting?

I would first make sure that the firewall on the remote machine is off, or at least customize the rules in a way that allows RPC traffic. Most new installations of Win7 have the firewall enabled by default, which would block any connections.

Then, make sure that the "Windows Management Instrumentation" service is running, though if that service were stopped now WMI capabilities would be available.

Finally, you need to make sure that you have proper access to the remote computer, but that is something that seems to be explained in the article you mentioned.

  • I updated the links, The most common error which I have is (error "DCOM Access Denied" decimal -2147024891 or hex 0x80070005) , but believe me which I tried every single step in the articles which I post. I check the firewalls (disabld and enabled), the DCOM access, The WMI services. so because of that I am looking for a guide to check and resolve this kind of issues.
    – Salvador
    Commented Jul 21, 2011 at 3:04
  • Thanks for the update. Are the computers in the same domain, or are the computers in a workgroup or a different domain? Another thing to check, is whether you have non-WMI related access to the remote computer in question. For example, can you open up "Services" and connect to the remote computer? Can you connect to remote shares (e.g. C$ which is only available to admins) on the remote computer?
    – Lucky Luke
    Commented Jul 21, 2011 at 13:25
  • 1
    According to the article, Administrators have access by default to WMI, and this is my experience also (I never had a problem connecting remotely in a domain). What application are you using to test WMI Access? Are you using a script or a software product?
    – Lucky Luke
    Commented Jul 21, 2011 at 13:29
  • Lucky finally, I found the problem the MSDN documentation does not mention the point about the Windows Group Policy in the Sharing and security model for local accounts, sometimes the remote logons are coerced to the guest account
    – Salvador
    Commented Jul 22, 2011 at 3:48
  • Great, glad you figured it out. What did you have to configure to make it work? This might help somebody who will run into this in the future.
    – Lucky Luke
    Commented Jul 22, 2011 at 21:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .