key factors to navigating the cloud- read

Brian Wren (Whom I will dub “the undisputed master of Management Pack authoring training at Microsoft”) presented an interesting session today on the types of interaction we can do between System Center Operations Manager and Orchestrator. The following is my summary from the session:

Key Notes:

  • Brian introduced the components of the Operations Manager IP for Orchestrator (items like Create Alert, Get Alert, Get Monitor, Monitor Alert, Monitor State, Start Maintenance Mode, Stop Maintenance Mode, Update Alert) and showed what these do and how they work.
  • Brian also showed some additional extensions to this type of functionality including the following extensions:
    • Start SCOM task: Operations Manager integration pack.
    • Start a runbook from OpsMgr: (Brian mentioned that InFront has a management pack which does this as well)
  • Notifications: OpsMgr notifications are a single step, with Orchestrator we can create a much more complex form of notification.
  • When to use Orchestrator versus OpsMgr diagnostics and recoveries:
    • Runbooks have access to information that Operations Manager may not have since diagnostics/recoveries run on the agent.
    • Situations where we need to assess information from a higher level than a single agent seems to be a great area to start using Orchestrator for.
  • Diagnostics/Recoveries: You can use a recovery in OpsMgr which runs a runbook in Orchestrator (calling it through the web service)


  • Calling OpsMgr tasks from a runbook in Orchestrator:
    • Brian showed using the Purge Queue task via a PowerShell script which he used to specify the task, class and instance information. It runs the tasks, and watches for status until it completes or times out.


(Brian, great job on the session and great usage of zoomit to show the details to the audience!)

And thank you to Thom Davis for the graphics above!