Skip to content

Orchestrator Integration Packs for System Center 2012

07/13/2012

In a previous article I discussed how imported os Integration Packs (OIP) for the Orchestrator to integrate Active Directory tasks in a package of actions, or Runbook Integrating System Center Orchestrator 2012 with Active Directory

In this article we will see how to install the Integration Pack for all products in the System Center suite 2012.

The first step is to download the file OIP in link http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=28725

Tip: If you want to know all the existing Integration Packs and how to configure them to access http://technet.microsoft.com/library/hh295851

Then register the Integrations Packs using the Orchestrator Deployment Manager as shown in the article cited at the beginning of the integration article.

Opening the Orchestrator Designer now will have available the actions of each of the products, which I’ll discuss next, and are available the versions 2007 and 2012.

System Center Data Protection Manager 2012

The DPM actions allow you to create restore points, retrieve data from SharePoint, SQL, and Hyper-V VMs. It is not possible for the actions to restore files, but this can be done through the component Run DPM PowerShell Script.

12-07-2012 13-17-54

System Center Configuration Manager 2012

Allows you to manage collections, adding or removing machines, send programs, applications, operating system updates and upgrades.

The actions that manage collections are importantissimas because as the Orchestrator allows you to add machines using Automation, as for example VMs, these components of the SCCM 2012 enabled us to add a new machine within a particular collection, which is the focal point of the SCCM for distribution and administration environment.

12-07-2012 13-18-10

System Center Operations Manager 2012

Geared exclusively to start operations, these components allow you to monitor specific alerts or events, put the machine in maintenance mode to perform other corrective tasks, close the alert and take the machine in maintenance mode.

With this we would have a perfect workflow, where an alert causes an action to be taken automatically without creating new alerts, the machine was put into maintenance mode, do any other task from another Integration Pack and the end close the alert and return the machine for monitoring in the Cockpit.

12-07-2012 13-18-27

System Center Service Manager 2012

As well as the Operations Manager components, this is intended to control scheduled operations, allowing you to create some incident types, relationships and monitor some objects.

An example of how this integration will be used is to create a Change when a determining Runbook is running to be monitored and at the end of the process to be updated with information to record in the KB of the Corporation.

12-07-2012 13-18-53

System Center Virtual Machine Manager 2012

This is the main reason of all the Integration Pack for System Center 2012, since all others are limited to application functions and basic management.

The number of items available in stock and component diversity shows how really is the most comprehensive and primary tool to be managed, which makes sense since the focus of the System Center 2012 is the management of private and public clouds.

We note that it is possible to create, change, and delete records, VMs and roles. Change the State of the virtual machines, create services from templates and even the creation of snapshots and network adapters in the virtual switch is possible.

12-07-2012 13-20-50

Creating a Runbook for System Center 2012

12-07-2012 13-28-57

The above example will stop a virtual machine to do Windows updates and change the size of the virtual disk.

  1. Initializes the data from servers that are entered in the settings of each Integration Pack
  2. Creates a Change in the Service Manager 2012
  3. Puts the server in maintenance mode in SCOM 2012
  4. Stop the virtual machine in VMM 2012
  5. Changes the size of the VHD in VMM 2012
  6. Changes the properties of VM, entering in the description the modification date
  7. Starts the virtual machine in VMM 2012
  8. Makes the deploy Windows updates by SCCM 2012
  9. Retire machine of maintenance mode in SCOM 2012
  10. Changes the Change in Service Manager to complete it
  11. Sends an email to the administrator stating the result of the operation

As can be seen, the whole process will occur automatically in minutes, integrating SCSM, SCCM, SCOM and VMM to perform an action in common.

Advertisements
Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: