Forum Discussion
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?
When you did the WBEM testing (which worked right?), did you use the credentials of the non-admin service account? Was it also run from the Collector server itself?
- lucjad2 months agoNeophyte
Yes, yes, and yes.
- lucjad2 months agoNeophyte
Do you know what would be the next step to troubleshoot it?
- JosiahBenoit2 months agoNeophyte
Hi Lucjad, does the password on the non-admin account have special characters "#&*^" ? that was my issue when dealing with Postgres
- lucjad2 months agoNeophyte
it does have special characters but I am not sure that would affect the whole process.
- Mike_Moniz2 months agoProfessor
It is likely best to work with LM support since they can look at your specific portal and situation. If you do, please let us know what it ended up being, in case it helps others.