In the upcoming whitepaper entitled "Using Veeam solutions to augment System Center and Hyper-V" Pete Zerger and I discuss how the Veeam management pack can be used to enhance the functionality available in System Center. Specifically we focused on how the new Hyper-V functionality could be leveraged for additional benefits in System Center.

While integration of this information is new for Hyper-V, the same idea to integrate VMware information into Service Manager has been done in the past. The following two blog posts cover these topics and provide additional readings which may assist with putting this in place for Hyper-V:

This blog post will cover the following topics for how to integrate the Veeam Hyper-V objects into the CMDB: finding the Hyper-V objects, finding the correct management packs, importing required management packs, whitelisting, adding the CI’s, creating the Hyper-V views, and show how the CI’s are integrated into Service Manager.


Finding the Hyper-V objects:

To find the class name for Hyper-V devices use the Discovered Inventory view in the Monitoring paneThis shows that "veeam hyper-v" is what I care about for these devices in Operations Manager.

While there are 30 targets, but for the views in Service Manager we are focused on the following key items in Hyper-V:

  • Clusters
  • Hosts
  • VMs

To find these objects we can look at the existing views in the Veeam management pack:

All Clusters:

All Hosts:

All VMs:


Finding the required Management Packs

To find the appropriate ManagementPackName which contain the objects we can use OpsMgr 2012 PowerShell:

Get-SCOMClass | Where-object {$_.Displayname –match "Hyper-V cluster \(Veeam MP\)"}

Get-SCOMClass | Where-object {$_.Displayname –match "Hyper-V cluster \(Veeam MP\)"}
| fl | more

Get-SCOMClass | Where-object {$_.Displayname –match "Hyper-V host \(Veeam MP\)"}

Get-SCOMClass | Where-object {$_.Displayname –match "Hyper-V host \(Veeam MP\)"}| fl | more

Get-SCOMClass | Where-object {$_.Displayname –match "Hyper-V virtual machine \(Veeam MP\)"}

Get-SCOMClass | Where-object {$_.Displayname –match "Hyper-V virtual machine \(Veeam MP\)"} | fl | more

The result indicates that I need to add a variety of classes which are included in the Veeam.Virt.Exentions.HyperV.Library management pack.


Importing required management packs:

I found that I needed the following management packs to get my lab environment to synchronize these hyper-V devices as CI’s:

The full list of MP’s in order is:

  • Microsoft.SystemCenter.2007
  • Veeam.Virt.Extensions.VMware.BaseDiscovery
  • Veeam.Virt.Extensions.HyperV.Library
  • Veeam.Virt.Extensions.HyperV.Discovery

(Note: I found the Microsoft.SystemCenter.2007 in the Management Packs for Update Rollups folder).

The VMware dependencies in Service Manager are shown below:



By allowing SCSM to import Veeam Hyper-V classes into the CMDB via the SCOM CI Connector, a richer set of host properties for the Hyper-V servers can be populated in the CMDB. This scenario is enabled through a process known as whitelisting. Once these CI’s are available within SCSM they can be used in change control processes and are easy to identify through views which can be created for these specific CI’s as shown below. For details on how to whitelist these types of objects see Pete’s blog post at


Adding the CI’s

Once the management packs have been loaded, the appropriate classes have been whitelisted and the appropriate management packs are checked on the connector then the connector can be synchronized.

After successfully synchronized the CI types with Veeam in the name appear as shown below.


Creating the Hyper-V views:

In Service Manager in the Configuration Items view, I created a folder called "Hyper-V". After this I created a view for each of the major pieces of the Hyper-V Infrastructure based upon the class list shown below:

Hyper-V clusters:

Hyper-V hosts:

Hyper-V Virtual Machines:


How are the CI’s integrated into Service Manager?

As expected these Hyper-V related devices also integrated correctly into Service Manager such as in the example below where a Hyper-V host is being added to an emergency change request.

Details for these objects are there as expected and shown below.


Summary: Due to the common structure between Operations Manager and Service Manager, the process of integrating CI’s from Operations Manager works as expected. Through using the Veeam management pack, we can now easy integrate Hyper-V clusters, hosts and virtual machines to effectively integrate these configuration items into the CMDB. The sample management pack for these HyperV views are available for download at: