In the Orchestrator 2012 R2 Installation article I have described the process of installing System Center Orchestrator from scratch, in this post I will go through the process of registering integration packs for the automation of different tasks.
Orchestrator Integration Packs – Overview
When installed Orchestrator comes with circa 40 built-in workflow standard activities which can perform a number of tasks and functions to make you immediately.
Orchestrator’s real strength lies in the ability to integrate with other Microsoft, like Exchange or other System Center products, and third-party products like VMware the integration is possible through the implementation of Orchestrator Integration Packs.
Orchestrator Integration Packs – Installation
For demonstration purposes I will be deploying Active Directory Integration pack which can be used to automate tasks like user account creation and management.
Once you have downloaded the file simply double-click on it and accept the license warning extracting the file to a convenient location
Orchestrator Integration Packs are contained in files with the OIT Extension and are imported through the Deployment Manager component
Review the summary page and again accept the license warning
Once Integration Pack registration is complete it will appear in the Integration Packs node of the Deployment Management Console together with name and version of the integration pack
Orchestrator Integration Packs – Deployment
Once the integration pack has been registered with the Deployment Manager to make it available to Runbook Servers you need to deploy it, in the Deployment Manager Console right-click the Integration Pack to deploy and select Deploy IP to Runbook Server or Designer
In the first page of the wizard click next and then select the IP(s) that need to be deployed to the Runbook Server
Next you will be asked to select the Runbook servers you want to deploy the Integration Pack to
The Integration Pack deployment can be scheduled during a service Window and you have the option to either stop all running Runbooks before the deployment or install even with running runbooks (which could lead to the need of a reboot)
You will again be presented with a summary of the tasks and then the deployment will start
You can monitor integration pack deployment in the bottom pane of the Deployment Manager Console
Once the integration pack has been deployed to the server it will be visible in the Designer console
Once the Integration Pack is available in the Designer console it can be used right away to start automating tasks.