Importing System Center Orchestrator 2012 Integration Packs

Author by Nathan Lasnoski

Orchestrator is already a powerful tool if all you could do is execute PowerShell commands.  That's not all you can do however.  Microsoft has constructed integration packs for many different server technologies that make automation simpler and easier.  This post walks through importing the System Center management packs into System Center Orchestrator's management server, then distributing them to the runbook servers.    Why are the two components separate?  The benefit of separating the components logically is that you can (1) have more than one runbook server and (2) you can stage integration packs and deploy during a period when you can make changes to the automations you have executing.  It also allows you to test integration packs in a development Orchestrator environment prior to deploying into production.  

Importing the Integration Packs

Let's get started.  First, we'll open up our deployment console and select to register the integration packs with the server.     Next, we'll select the integration packs we want to register.     After the registration has been completed we'll deploy the management packs to the runbook servers.    We'll then select the integration packs to deploy.  This will give you the option of terminating current runbooks, or deploying without terminating.     Deployment will look like this...  


Finding Orchestrator Integration Packs:

Where do I find Orchestrator integration packs?  A few places.    Active Directory (RC):   System Center 2012 integration packs (RC).   Exchange and others… (Codeplex):   IBM integration packs (RC):   Vmware vSphere (RC):   HP (RC):   SharePoint (community):   Windows Tasks (community):    F5 Load Balancer (community):   Social Media (community):   Download site with filter:   Happy automating!   Nathan Lasnoski


Nathan Lasnoski

Chief Technology Officer