What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

WMI Permission denied

Votes:

0

Since removing all our domain and going through Beyond Trust, the WMI sensors have been defective

The user that is inserted into PRTG is a member of the following groups

Distributed COM Users Remote Management Users Service Admins

Does it need to be apart of anything else apart from the domain admin group

permissions prtg wmi

Created on Nov 27, 2019 9:44:00 AM



4 Replies

Votes:

1

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]

Created on Nov 27, 2019 6:30:02 PM by  Jonathan Mena [Paessler Technical Support]



Votes:

0

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

Created on Nov 28, 2019 4:16:00 PM



Votes:

0

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.

Created on Nov 29, 2019 6:52:40 PM by  Jonathan Mena [Paessler Technical Support]



Votes:

0

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!

Created on Jun 16, 2022 6:23:31 PM




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.