Home » System Center Service Manager » Business Services in Service Manager


Welcome to contoso.se! My name is Anders Bengtsson and this is my blog about Azure infrastructure and system management. I am a senior engineer in the FastTrack for Azure team, part of Azure Engineering, at Microsoft.  Contoso.se has two main purposes, first as a platform to share information with the community and the second as a notebook for myself.

Everything you read here is my own personal opinion and any code is provided "AS-IS" with no warranties.

Anders Bengtsson

MVP awarded 2007,2008,2009,2010

My Books
Service Manager Unleashed
Service Manager Unleashed
Orchestrator Unleashed
Orchestrator 2012 Unleashed
Inside the Microsoft Operations Management Suite

Business Services in Service Manager

Business Services in Service Manager 2010 is a way for you to present your services, both IT components within it and properties of it like affected users and SLA level. Business Services often start in Operations Manager as a distributed application. You then import the same management packs into Service Manager to get the structure of your application. After that you use a Operations Manager connector to synchronize components of your distributed application into your business service in Service Manager. In this post I will show you how you could do that.

I have created a simple distributed application in Operations Manager. It is stored in a management pack named “Contoso – myService”.

  1. What you need to do first is to export the management pack from Operations Manager and import it into Service Manager. You do that from the Administration workspace in both products. Note that you need to import all the management packs that contain a component from your distributed application. For example if you have created a web application check in MP01 and stored your distributed application in MP02, then you need to import both of them. Else, you will not see all components in the business service in Service Manager.
  2. If this is the first management pack you move over to Service Manager you will probably get a message like this
  3. The management pack you try to import depends on a number of other management packs and these needs to be imported first. Most o f these you can either download from Microsoft webpage or import from the installation folder of your Operations Manager Root Management Server.
  4. Once the management pack with your distributed application is imported into Service Manager you will see it under Business Services in the Configuration Items workspace. However there will not be any components in it until you enable synchronization.
  5. Navigate to the Administrator workspace, expand connectors and open your Operations Manager CI Connector. Refresh the list of management packs and select to synchronize your management pack. Save the setting and start the synchronization of the connector.
  6. After some time, open the business service configuration item and look at the component tab

You can now fill in the other properties of the business service.  

What if you want to get alerts from Operations Manager to show up as related incidents, for your service in Service Manager?  Service Manager will not connect related incidents and services to each other by default. For example if I get an alert about C: on a logical disk that is in my service component list, the incident will not show up as a related item on my service. The service will not either show up as a related item on the incident. To get this to work you need to generate an alert with the same as the service. In my case an alert named “Contoso – myService”. This can be done with some planning and a couple of dependency rollup monitors in Operations Manager.

Summary: Busniess Services in Service Manager can be used to represent your services within Service Manager. You can merge data and components from other systems like Operations Manager and Configuration Manager and present it as a service. In Service Manager you can fill in information like SLA for the server, contact persons and customers.

Remember that if you change the class structure of your distributed application, dont forget to update the management pack in Service Manager too. If you need to get your incidents in relationship with your services automatically, then start by planning this on a piece of paper, and then create necessary monitors in Operations Manager.


  1. I remember something around this for SCSM 2010. When updating the service manager side with a new MP, you needed to delete the business service and then re-configure everything, like owner and customers. To get alerting to work you must generate an alwert with the same source as the service name. You can accomplish this using an extra dependency rollup monitor in Ops Mgr.You can also override and configure one of the default aggregate rollup monitors in the distributed application health model to generate an alert. A disadvantage of this is that you cannot control the alert description.

  2. Greetings Anders.

    Would it be possible to know how to create that specific rollup monitor in SCOM so my alerts get related to the service?

    My problem is that, im worked with the unsealed versions of the MPs, so when I try to create any type of monitor over my DAs I got an error of not being able to reference unsealed MPs.

    If I seal them via MPSeal and the key,after deleting the unsealed versions, SCOM reimports with no problem, yet SCSM doesn’t allow me to.

    Should I be working with sealed or unsealed versions of my custom MPs?
    Is there any way to get the alert rolled up to the service in SCSM with the sealed versions of the MPs?

    Thanks for your help.


  3. Anders, I saw this at MMS 2010 and really like how everything is connected and centralized. Great work on the post!

Leave a comment

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.