WMI Permission denied

Hello Iand,

Thank you for contacting us,

Regarding the WMI user access, make sure the password is the same, also the windows user have to be included in the user groups "Performance Log Users" or "Performance Monitor Users", "Remote Desktop Users" and "Distributed COM Users". You also need to enable permissions and services. For more detailed information you can refer to this guide

This has been discussed in our knowledgebase, so you might consider to check out the feedback of PRTG users and additional hints here and here And you can get some more information about the user access settings in this article as well as in this one

We have seen cases where an user is created with exactly all the admin rights in the correct groups and still doesnt work. But when using a local administrator user it works fine. Even with all the same exact access and permissions. This is an issue in the windows side and not from the PRTG perspective but is also something to take into consideration when testing.

Please also see our extensive WMI Troubleshooting Guide it may contain some more information.

If you keep having problems please use our WMI Tester, run it on the PRTG Host (or host of the Remote Probe) and scan against this particular target, usually the "OS-Query" from the "Advanced" Tab of the Tool works best, please send us the Results on a ticket to [email protected]

I have muddled this now and managed to get the sensors to work however the Active directory sensors are still not working via WMI

Iand,

I'm glad the WMI sensors are working fine now. Regarding the Active Directory sensors there may be something else missing in the configuration. In order to know for sure, please contact the support team by sending a support ticket to [email protected] with all the relevant information so it can be analyzed further.

The WMI test tool was instrumental in helping us resolve this issue. After a Microsoft Patch Tuesday , non of the patched servers responded to WMI inquires from the PRTG server. We got Access Denied. The test tool found the same. Then we ran the tool on the domain controller that wasn't responding and found that all the servers responded. Our PRTG server was still running on Windows 2008 R2 and the target servers were 2012 R2 or newer. I migrated the PRTG installation to a 2019 server and everything works!