Additional configuration steps specific to SCOM 2019

Description

If the Run As account does not have “Log on as a Service” permission, an error event 7002 is logged in Operations Manager event log by Health Service on Agent computer(the Enterprise Vault server configured for SCOM monitoring).

• To resolve this, provide “Log on as a Service” permission to the applicable Run As accounts, which are identified in the event 7002.
• Refer section "Enable service log on permission for Run As accounts" in following link for more details:
  https://docs.microsoft.com/en-us/system-center/scom/enable-service-logon?view=sc-om-2019

If the Run As account does not have sufficient privileges to monitor and collect Windows performance counter data, an error events 10143 and 10144 is logged in Operations Manager event log by Health Service on Agent computer. As a result, all the monitors and rules based on performance counters will not reflect correct health status.

• To resolve this issue, you need to add Run As account to “Performance Monitor Users” computer group on Agent Computer.

When you install System Center 2019 Operations Manager together with the latest version of SQL Server Reporting Services (SSRS) 2017, Operations Manager reports do not deploy. When you open the Reporting view in the Operations console and select any of the folders, the list of reports is empty. Additionally, an error event 31567 is logged in the Operations Manager event log.

• To resolve this, follow one of the resolutions provided in the following link:
  https://docs.microsoft.com/en-US/troubleshoot/system-center/scom/cannot-deploy-operations-manager-reports