One of the key selling points in System Center Service Manager (SCSM), is the way it integrates with other systems and how it populates and updates the SCSM CMDB automatically.

By configuring connectors for System Center Configuration Manager, System Center Operations Manager and Active Directory you can have a dynamic CMDB in just a few clicks.

Just a note, this post will not go into detail about setting up the connectors for SCCM and AD. It will focus mainly on SCOM and how you can use SCOM to automatically populate your CMDB.

Customer request – The Good, the Bad and the Ugly 41NjY9JrEoL

A common question I receive from every customer is “I want a Dynamic CMDB but what about the non-standard objects?”

From my experience, in most SCSM projects you can end up in a sort of standoff.

Just like a scene from the film ‘The Good, The Bad and The Ugly’.

I’ve noticed that there’s always that one person who has waited the whole session on SCSM and how it integrates, with their question. They have thought about their question and from their experience and knowledge on “other” products. They are waiting to fire their question.

“Yeah, Microsoft but what about the non-Microsoft products? We have “tons” of other stuff like VMware, Oracle and Linux?” They say with a grin followed by “You cannot use Microsoft for these, so how are you going to populate these?”

The room is filled with silence and all eyes are on you. From my experience you can wait for The Ugly to stand by them, he is the person who has been working with the “old” system and doesn’t want to migrate.

He says “Yeah without these we cannot use a dynamic CMDB how are YOU going to cope with that?”

Now this is exactly the position I want to be in. I know these guys and if you have seen “The Good, The Bad and The Ugly” you know you’ll need to make this work in your favor or remove the bullets from one of them, leaving you with one left. The one who is slow on the trigger, because he is using old ammo.

Now all you need some help to remove the guy’s bullets right?

The solution

First, the Linux systems. This hasn’t been much of an issue ever since 2012, where we can monitor these with SCOM and once monitored you can pull them with the SCOM CI connector to SCSM.

The next parts are harder though, this is where a third party solution comes into play.

This particular case was solved by Opslogix, who provide both VMware and Oracle monitoring for SCOM.

I installed the VMware pack in SCOM and waited for all of the VMware components to be discovered. There was also a great manual available to easily install the components in SCOM.

Additional information can be found at the following websites:

Dieter Wijckmans – Jedi and MVP – Test drive Opslogix VMware management pack

Stanislav Zhelyazkov – MVP – First Look at OpsLogix’s VMware Management Pack

Arjan Vroege – System Center Dashboarding Guru – OpsLogix VMware Management Pack and Dashboarding capabilities

Prepare SCSM for SCOM CI Connector

First, you will need to install the SCOM management packs, just import them in SCSM.

These packs can be found in the install directory of SCSM:

C:\Program Files\Microsoft System Center 2012 R2\Service Manager\Operations Manager 2012 R2 Management Packs\

vmware components in system center service manager

After importing these packs, you can import the OpsLogix management packs.

Before the actual import you will need to add two management packs which are required by the OpsLogix packs.

vmware components in system center service manager

NOTE*** The Microsoft.SystemCenter.Visualization.Library.mpb file is a Bundle and NOT the MP!

You can find the management packs on the SCOM installation media, in the folder “ManagementPacks”. Again, ensure you use the MPB of the Microsoft SystemCenter Visualization Library.

After this you can import the OpsLogix management packs in SCSM:

vmware components in system center service manager

After adding the management packs, you can add the OpsLogix VMware classes to the SCSMAllowlist

You can use the PowerShell Script below in a PowerShell Session: (Be sure to change the drive if you installed service manager on an alternative drive)

Import-Module ‘C:\Program Files\Microsoft System Center\Service Manager 2012\Powershell\System.Center.Service.Manager.psd1’

Add-SCSMAllowListClass -ClassName ‘OpsLogix.IMP.VMWare.Cluster’

Add-SCSMAllowListClass -ClassName ‘OpsLogix.IMP.VMWare.Datacenter’

Add-SCSMAllowListClass -ClassName ‘OpsLogix.IMP.VMWare.Datastore’

Add-SCSMAllowListClass -ClassName ‘OpsLogix.IMP.VMWare.ESXServer’

Add-SCSMAllowListClass -ClassName ‘OpsLogix.IMP.VMWare.Network’

Add-SCSMAllowListClass -ClassName ‘OpsLogix.IMP.VMWare.vCenter’

Add-SCSMAllowListClass -ClassName ‘OpsLogix.IMP.VMWare.VirtualMachine’

The last thing you need to do is configure the SCOM CI Connector. In order to do this, you’ll need a Service Account with SCOM Administrator rights.

In SCSM navigate to Administration\Connectors

vmware components in system center service manager

Add the Operations Manager CI Connector.

Make sure you select all management packs for synchronization:

vmware components in system center service manager

The last step is to synchronize the connector to synchronize your VMWare components into SCSM.


Finally, you will create views in your Configuration Item pane to show the VMware components in SCSM.

vmware components in system center service manager

vmware components in system center service manager


If you want to walk away alive during the session (or show down) on SCSM Dynamic CMDB, you will need to know how to remove the bullets from The Bad.

Although I like to think of myself walking away like Clint Eastwood did, smoking a cigar and spitting in the sand, but I still require the bullets to shoot back.

The OpsLogix management packs gave me the perfect way to remove the bullets from The Bad and silence The Ugly once and for all.

The credits all go to OpsLogix Support!

While testing this solution, I discovered that the original VMware pack had an issue, since SCSM likes to look at things from a Configuration Item perspective, its required classes are underneath the Configuration Item Abstract class, which they weren’t.

As this was not a minor change, I was really impressed by the support delivered by the OpsLogix team. They redesigned and replaced the VMware classes below the configuration item class which makes them inherit the correct properties to be in SCSM. They were able to complete this all within one week!

So take a look at the VMware management pack and how you can fill your dynamic CMDB.

Thanks Guys!

Oskar Landman


You can read the original blog here.