Menu Close

New Administrative Console Views in SCOM 2019

In the SCOM Console you will see some new views in the Administration panel:


These actually aren’t new for SCOM 2019, they existed in 1801/1807 as well. 

These are driven by a Management Pack discovery, in the MP: Microsoft.SystemCenter.OperationsManager.Internal (Operations Manager Internal Library).  The new discovery is Microsoft.SystemCenter.OM.Products.Discovery (Discovery of Operations Manager deployment).

You will see things like Management Servers, Gateways, Consoles, etc.

One thing to note – this discovery only runs once per day, on ALL health service objects in the management group.  You might notice that your first Management Server that hosts the RMS Emulator (root health service) is not discovered, nor are the Databases.  The most common reason for this, is that we require an agent to be deployed to the SQL Servers that host the SCOM OpsDB and DW.  When the RMS discovery runs, it also discovers the instances for the SCOM databases, but discovers them for the Computer that hosts those DB’s.  If that Computer doesn’t exist in SCOM, this discovery will throw an error.  You might see this in the SCOM event logs on the missing Management Server:

Log Name:      Operations Manager
Source:        Health Service Modules
Event ID:      10801
Discovery data couldn’t be inserted to the database. This could have happened because  of one of the following reasons:

     – Discovery data is stale. The discovery data is generated by an MP recently deleted.
     – Database connectivity problems or database running out of space.
     – Discovery data received is not valid.

The following details should help to further diagnose:

DiscoveryId: 55f32a19-b0db-3a12-83d8-414183ff13b4
HealthServiceId: e1259bd6-c694-7eea-187c-809dd305f829
Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceException,The relationship source specified in the discovery data item is not valid.
Relationship source ID: 766eca98-7454-9141-0b3d-745545358e82
Rule ID: 55f32a19-b0db-3a12-83d8-414183ff13b4
<?xml version=”1.0″ encoding=”utf-16″?><RelationshipInstance TypeId=”{b22d9165-494b-5fa8-57af-f2c608e103bc}” SourceTypeId=”{ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd}” TargetTypeId=”{3b6a3bec-2355-8c6a-4d8d-fc9ec20d4282}”><Settings /><SourceRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name><Value></Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name><Value></Value></Setting><Setting><Name>c631cdcb-89b0-7ac0-840c-8301b557249c</Name><Value></Value></Setting><Setting><Name>df750e2d-8323-25d2-0613-051bbc8bafaf</Name><Value>Operations Manager Database</Value></Setting></Settings></TargetRole></RelationshipInstance>.

Simply deploy an agent to the SQL Server(s) hosting the OperationsManager and OperationsManager databases.  Then wait 24 hours, or restart the Microsoft Monitoring Agent (HealthService) on the missing management server.






So in summary – if you have multiple management groups deployed, and want to use these views, you will have to ensure that the SQL servers hosting the SCOM DB’s have an agent that is connected to the SCOM Management group that it supports.


  1. Kester Stoner

    Hi Kevin,

    I have SCOM 1807 and both SQL servers have an agent installed, however both RMS and Database servers were never discovered in this view. Anything else to look into ?


    • Kevin Holman

      Restart the health service on the RMSe. Then, after 10 minutes or so, look for a 10801 event. This is a discovery rejection. See if that gives you any clues.

      • Kester Stoner


        The below alert was prompted, (I have pasted parts of it below)

        Discovery data couldn’t be inserted to the database.
        Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceException,The relationship source specified in the discovery data item is not valid.
        Rule name : Discovery of Operations Manager deployment

        • Kevin Holman

          on the management server, in the registry, at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatabaseServerName string value – does what is in here match the FQDN of a Windows Computer object in your environment?

          • Kester Stoner

            It has the SQL Always on listener (not in FQDN) on where the omdb is hosted followed by the port.

  2. Simon

    Hello do you have any update on this error. It driving me crazy. I find absolute no solution for this.
    Thanks in advance

Leave a Reply

Your email address will not be published. Required fields are marked *