This article applies as of PRTG 24

Since switching to Beyond Trust, our WMI sensors in PRTG have stopped working. The PRTG user is in Distributed COM Users, Remote Management Users, and Service Admins groups. Does it need to be in any other groups besides Domain Admins?


Regarding the WMI user access, make sure the password is the same, also the Windows user has 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 Knowledge Base, so you might consider checking 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 a user is created with exactly all the admin rights in the correct groups and still doesn't work. But when using a local administrator user it works fine. Even with all the same exact access and permissions. This is an issue on 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 as 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 in a ticket to support@paessler.com.



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.