WMI Service Sensor does not display *ALL* Windows Services

Hello,

The sensor is using the following WQL query to list all services:

SELECT Name,Caption,Description FROM Win32_Service

Usually this should list all available services from services.msc. You can test the query manually by using our WMI Tester. Do you see the missing service here?

I performed this test within the PRTG WMI Tester using the custom query that you provide but the service in question plus many other services did *NOT* appear. "Services.msc" on the Windows server lists a lot more services than WMI Service Sensor or the WMI Tester Tool. How do we make these synch up and display everything that "services.msc" shows? Thank you!

I'm afraid in this case it seems like there's an issue with your WMI class "Win32_Service". To fix this, you can try rebooting the server once (if not already done). Otherwise the following article might help as well: https://kb.paessler.com/en/topic/3713

Rebooting the monitored server was attempted but that didn't address the issue. I did want to mention that the local account that we use for WMI monitoring is not the local "administrator" account. We created a local account by another name and applied the following to enable WMI to function:

wmic useraccount where name="LOCALACCOUNTNAME" get name,sid

sc sdset scmanager D:(A;;CC;;;AU)(A;;CCLCRPRC;;;IU)(A;;CCLCRPRC;;;SU)(A;;CCLCRPWPRC;;;SY)(A;;KA;;;BA)(A;;CC;;;AC)(A;;CCLCRPWPRC;;;LOCALACCOUNTNAMESID)S:(AU;FA;KA;;;WD)(AU;OIIOFA;GA;;;WD) 

Even after running the above commands for the local account, is it possible that more permissions might still be needed for WMI Service Sensor to display *ALL* services that "services.msc" on the Windows server contains? Thanks again for your continued support!

Im afraid, its difficult to limit the permissions that are required for WMI Sensors, since it depends on multiple factors like group policies, firewall, other domain restrictions etc. I'm afraid we can't tell how those permissions can be limited exactly for your infrastructure. That's why we always recommend to use the domain administrator.

If the above mentioned guide did not solve your issue, could you try using a administrator account instead for testing purposes to see if the issue might be related to missing permissions?