realscom

ID: 1102 Log: Operations Manager Source: HealthService Description: Rule/Monitor "Microsoft.SystemCenter.DataWarehouse.Deployment.Report" running for instance "Data Warehouse Synchronization Service" with id:"{EA0B5D81-9F4F-9C47-8286-0B6549506B22}" cannot be initialized and will not be loaded. Management group "C03MWSSCOM" I got this when the scom reader account wasn't allowed to log on to the mgmt servers. They'd done this in 2 ways; firstly they denied "Allow log on locally" in group policy to the reader account, secondly, in AD they locked down which computers the reader account could log in to. When both these issues were resolved you'll start seeing 31568, 31570 (Type=Information, Source=Health Service Modules) and the reports starting being populated in the Reporting pane in the console.

The original article explaining this is here: https://blogs.technet.microsoft.com/kevinholman/2016/08/25/sql-mp-run-as-accounts-no-longer-required-2/ Environment: My SCOM 2012 R2 lab. I had already installed SQL MP version 7.0.2.0 which covers SQL 2005 - 2012 [need to confirm versions] Steps in order: The only instance I had to test with was my SCOM one running SQL 2014 so I had to install version 7.0.2.0 of the 2014 mp. I installed these MPs (the others were already installed or weren't needed) Microsoft.SQLServer.2014.Discovery Microsoft.SQLServer.2014.Monitoring Microsoft.SQLServer.2014.Presentation Microsoft.SQLServer.2014.Views I didn't have to bounce the HealthService and the SQL instance appeared straight away in SCOM. It seemed to be monitored OK too. I'm guessing it's because it's the SQL instance for SCOM therefore has more access? I would think on a normal SQL server this wouldn't happen. I got this alert: SQL Server cannot authenticate using Kerberos