Apr 22 2024 08:43 AM
We built a SCOM 2022 environment with no issues in discovery all of our servers. I installed the SQL agnostic Managment Pack, latest version. I decided to leverage Kevin Holman's method of discovery SQL Server, avoiding the run as account. The SQL Seed Class is all Healthy. I checked the Registry to confirm, and all looks good.
Next step is for the SQL team to create an account to create a HealthService Login. They did that and when I ran the task Create HealthService Login as Low Priv Task, it was successful. Ran the run-as Demand Database Discovery. Get no error message and but all the servers are showing Not Monitored. I ran it via manual SQL script and looks good, no error, but still I am getting "not monitored".
Is there a log file that I can review or a method of seeing what is happening in the environment. I thought it might be network, but not sure. My second guess might be a group policy is preventing maybe a log on as a service, but that isn't the case and I set it up manually to log in as a service.
It would be great if there was an error, so hoping that this process is captured in some log. I checked Agent Management logs, and it has no information at all regarding SQL discovery.
Apr 30 2024 10:28 AM