SQL Server Services monitoring for non-admin account

Are you able to see some services but not others (like when using Add Other Monitoring)? Some services may require modifying their own ACLs on top of modifying scmanager's, and sometimes you need special permissions to even make those changes. I only played with Service SDDLs a little bit so don't know much myself. I would try looking at the thread below, especially comments by Barb that might cover it in a bit more detail. The thread well predates LM's official support page so I don't know how well they align though.

How WMI, DCOM, RPC and UAC effect access to remote Window Systems for Monitoring

Hi LucJad, I just went through this with my DBA's.  LogicMonitor seems to work better with the wmi.user and wmi.pass on the WinSqlServer- module.  What I had to do is add the wmi user and pass on the devices.  The issue is that after I did that, my DBA's were seeing Logon errors which pointed to my service account.  to resolve that they had to give LogicMonitor permissions to access SQL.  By the way WinSqlServer was superseded by Microsoft_SqlServer_GlobalPerformancehttps://www.logicmonitor.com/support/monitoring/applications-databases/microsoft-sql-server

I hope this helps let us know how it turned out 

JosiahBenoitI need SQL Server Services (Browser, Agent,...) monitoring for non-admin service account. Logic Monitor documentation doesn't have info about Logic Monitor's Active Discovery related to this specific issue. I set up permissions but Logic Monitor still doesn't pick anything up from server after running active discovery. 

Let me just start from beginning:

I have Collector server that has local admin service account to run SQL Services on Windows. That's Logic Monitor's requirement when adding Collector to monitoring. Under Collector server in Logic Monitor I see DataSource called SQL Server Services (WinSQLServices --> when you go to edit global definition). 

But it only works on this device added to Logic Monitor because the service account on the Windows Server itself has local admin privileges. That's why the WinSQLServices is discovered by Logic Monitor and it's listed under this device. 

I am trying to get the WinSQLServices to work on other monitored devices. All other devices monitored by Collector are not getting SQL Server Services discovered. I created non-admin service account so these services can also be monitored on all other servers that are under Collector. Documentation gives the instructions how to do it: make SDDL changes.(https://www.logicmonitor.com/support/getting-started/advanced-logicmonitor-setup/windows-server-monitoring-and-principle-of-least-privilege) I did SDDL changes to non-admin account has the same privileges as the local admin account. I ran active discovery in Logic Monitor but all other devices are still not even recognizing the WinSQLServices(SQL Server Services). 

Based on this documentation everything should work but it doesn't. Any chance there are more settings to look at?