Various Ways to Find the ID of a Monitoring Object in OpsMgr

4 minute read

Often when working in OpsMgr, we need to find the ID of a monitoring object. For example, in the recent Squared Up Dashboard  version 2.0 Customer Preview webinar (, it was mentioned in the webinar that the monitoring object IDs must  be located when preparing the Visio diagram for the upcoming Visio plugin.

In this post, I’ll demonstrate 3 methods to retrieve the monitoring object ID from SCOM. These 3 methods are:

  • Using OpsMgr built-in PowerShell Module “OperationsManager”
  • Using OpsMgr SDK via Windows PowerShell
  • Using SCSM Entity Explorer

In the demonstrations, I will show how to retrieve the monitoring object ID for a particular SQL database:

  • Monitoring Class Display Name: SQL Database
  • DB name: master
  • SQL Server:


Note: Before I start digging into this topic, if you are not very PowerShell savvy, and only want a simple GUI based solution, please go straight to the last method (using SCSM Entity Explorer).

Using OpsMgr PowerShell Module OperationsManager

01. Define variables and connect to the management server:

#region variables

$ClassDisplayName = "SQL Database"
$DBName = "master"
$SQLServer = ""


#Connect to OpsMgr management server
import-module operationsmanager
New-SCOMManagementGroupConnection -ComputerName OPSMGRMS01

02. Get the monitoring class based on its display name:

#Get the monitoring class based on the class display name
$MonitoringClasses = Get-SCOMClass -DisplayName $ClassDisplayName

However, in my management group, there are 2 classes with the same name “SQL Database”:


As you can see, the first item in the array $MonitoringClasses is the correct one in this case. We will reference it as $MonitoringClasses[0].

03. Get the monitoring object for the particular database:

$MonitoringObject = Get-SCOMClassInstance -Class $MonitoringClasses[0] | Where-object {$_.Name -eq $DBName -and $_.'[Microsoft.Windows.Computer].PrincipalName'.value -ieq $SQLServer -and $_.'[Microsoft.SQLServer.ServerRole].InstanceName'.value -ieq $DBEngine}

The Get-SCOMClassInstance cmdlet does not take any criteria, therefore, the command above retrieves all instances of the SQL Database class, then filter the result based on the database name, SQL server name and SQL DB instance name to locate the particlar database that we are looking for.


The monitoring object ID is highlighted as above.


The type for the ID field is Guid. You can also convert it to a string as shown above.

Using OpsMgrSDK Via Windows PowerShell

In this example, I won’t spend too much time on how to load the SDK assemblies, in the script, I’m assuming the SDK DLLs are already loaded into the Global Assembly Cache (GAC). So, in order to use this script, you will need to run this on an OpsMgr management server or a web console server, or a computer that has operations console installed.

01. Define variables, load SDK assemblies and connect to OpsMgr management group:

#region variables

$ClassDisplayName = "SQL Database"
$DBName = "master"
$SQLServer = ""

#Load SDK

#Connect to management group
$MGConnSetting = New-Object Microsoft.EnterpriseManagement.ManagementGroupConnectionSettings("OpsMgrMS01")
$MG = New-Object Microsoft.EnterpriseManagement.ManagementGroup($MGConnSetting)

02. Get the monitoring class based on the display name

#Get the monitoring class
$strMCQuery = "DisplayName = '$ClassDisplayName'"
$mcCriteria = New-Object Microsoft.EnterpriseManagement.Configuration.MonitoringClassCriteria($strMCQuery)
$MonitoringClass = $MG.GetMonitoringClasses($mcCriteria)


As you can see, since the display name is not unique, 2 classes are returned from the search (this is same as the first method), except this time, the type for $MonitoringClass varible is a ReadOnlyCollection. However, we can still reference the correct monitoring class using $MonitoringClass[0]


03. Get the monitoring object for the particular database:

Please refer to this page for the properties that you can use to build the search criteria (MonitoringObjectGenericCriteria)

#Get the monitoring object
$DBPath = "$SQLServer`;$DBEngine"
$strMOQuery = "DisplayName = '$DBName' AND Path = '$DBPath'"
$MOCriteria = New-Object Microsoft.EnterpriseManagement.Monitoring.MonitoringObjectGenericCriteria($strMOQuery)
$MonitoringObject = $MG.GetMonitoringObjects($MOCriteria, $MonitoringClass[0])

As you can see, unlike the first method using the built-in module, we can specify a more granular search criteria to locate the monitoring object (as result, the command execution should be much faster). However, please keep in mind although there is only one monitoring object returned from the search result, the $MonitoirngObject variable is still a ReadOnlyCollection:


And you can access the particular SQL Database (Monitoring Object) using $MonitoringObject[0]:


Using SCSM Entity Explorer

SCSM Entity Explorer is a free utility developed by Dieter Gasser. You can download it from TechNet Gallery:

Although as the name suggested, it was developed for SCSM, it also works with OpsMgr. Once you’ve downloaded it and placed on a computer, you can follow the instruction below to locate the particular monitoring object.

01. Connect to an OpsMgr management server and search the monitoring class using display name


As shown above, there are 2 classes returned when searching the display name “SQL Database”. You can find the correct one from the full name on the right.

02. Load objects for the monitoring class:

Go to the objects class and click on “Load Objects” button to load all instances.


Unfortunately, the we cannot modify what properties to be displayed on the objects list, and the display name does not contain the SQL server and DB instance name. In this scenario, the only way to find the correct instance is to open each one using the “View Details” button.


Once you’ve located the correct instance, the monitoring object ID is displayed on the objects list.

Having said that, if you are looking for a monitoring object from a singleton class (where there can only be 1 instance in the MG, such as a group), this method is probably the easiest out of all 3.

i.e. When I’m looking for a group I created for the Hyper-V servers and their health service watchers, there is only instance:


Also, for certain monitoring objects (such as Windows Server), you can easily locate the correct instance based on the display name:



based on your requirements (and the information available for search), you can choose one of these methods whichever you think it’s the best.

Lastly,  if you know other ways to locate monitoring object ID, please leave a note here or send me an email.

Leave a comment