Hello everyone, if you have been following along with my guides, you should now have Orchestrator installed.

Orchestrator includes over 41 built-in workflow standard activities that perform a wide variety of functions. You can expand Orchestrator’s functionality and ability to integrate with other Microsoft and third-party platforms and products by installing integration packs. Integration packs for Orchestrator contain additional activities that extend the functionality of Orchestrator.

For this lab example, we will download and install the System Center Integration Packs, which will enable Orchestrator to integrate with all the other System Center products.

Download Integration Packs

To start, open a browser and navigate to the following URL: http://technet.microsoft.com/en-us/library/hh295851.aspx, and click on the last link in the page labelled “Integration Packs for System Center”.

Integration Packs 01

On the Integration Packs for System Center page, you can choose either the 2007 or 2012 Integration Packs. For this lab example, we will use the 2012 packs.

Integration Packs 02

Click on the link for each System Center product, which will bring you to another webpage. Look for the link under the ‘Downloading the Integration Pack’ section. This will bring you to the download page.

Integration Packs 03

Click the Download button, and select all 3 items to download. Note, you do not need to download and install the Best Practice Analyzer, or the Integration Toolkit, but they are useful to have.

Integration Packs 04

After the files are downloaded transfer them to the Orchestrator server (if you didn’t download them directly).

Install Integration Packs

Start by running the System_Center_2012_Orchestrator_Integration_Packs.exe. You will receive the following prompt to extract the files. Either accept the default or change it to another directory, then press OK.

SC IP Install 01

When the extraction is complete, you will receive the following prompt. Press OK.

SC IP Install 02

If you open the directory where the files were extracted to, you will see a bunch of files ending in .oip file extensions. These are the Orchestrator Integration Packs.

SC IP Install 03

Now open the Deployment Manager.

SC IP Install 04

Before we can use the Integration Packs, we need to Register and Deploy them. We have to start with registering the packs. Right-click on the Integration Packs folder and choose ‘Register IP with the Orchestrator Management Server’.

SC IP Install 05

This will launch the Integration Pack Registration Wizard.

Here is a video walk through:

Register Integration Packs

When you choose ‘Register IP with the Orchestrator Management Server’ from the Deployment Manager, this wizard will launch. Click Next.

Register IP 01

On the Selection screen, click the Add button to find the Integration Pack(s) you want to register.

Register IP 02

In the Open dialog, browse to where the .OIP files were extracted to, and select the Integration Pack you want to register. Note that you can only select one at a time, and are not able to multi-select. You can, however, register more than one at once.

Register IP 03

If you want to register more than one Integration Pack at once, just click the Add button again and select another .oip file. Once you have the file(s) selected click Next.

Register IP 04

The next screen will list everything the wizard finds. Click Finish to start the registration.

Register IP 05

You will encounter an End-User License Agreement for every Integration Pack (meaning if you are importing 5 packs at the same time, you will have 5 agreement prompts). Read the information presented and press Accept.

Register IP 06

Once the registration is complete, the Integration Packs will now be present under the Integration Packs directory.

Register IP 07

Here is a video walk through:

Deploy Integration Packs

Now that the packs are registered with the Orchestrator server, we can now deploy them.

In the Deployment Manager, right-click the Integration Packs directory and choose ‘Deploy IP to Runbook Server or Runbook Designer’.

Deploy IP 01

The Integration Pack Deployment Wizard will launch. Click Next.

Deploy IP 02

Now select the Integration Packs that you want to deploy. On this dialog you can select multiple packs, but only the packs that have been registered will appear for selection. Make your selection and then click Next.

Deploy IP 03

Next you need to supply the computer(s) that you want to deploy to. If you recall from the context menu, this is either to a Runbook Server or a Runbook Designer. So this can be the Runbook Server (in our lab example, the same server running all the other Orchestrator elements), or the Runbook Designer (which can be installed on an Administrator workstation).

Add the various computer names, and then click Next.

Deploy IP 04

You can schedule the installation for the future (i.e. after-hours in Production), or install the packs immediately with the wizard. You also have control on how the installation will affect the system (i.e. stopping the Runbooks or not).

Make the applicable selections and click Next.

Deploy IP 05

Review the information on this final screen and click Finish.

Deploy IP 07

The wizard will deploy the Integration Packs.

Deploy IP 08

Once the Integration Packs have been deployed, in the Runbook Designer you will see the additions (in this example the System Center packs) on the right in the Activities pane.

Deploy IP 09

Now we need to connect the pack(s) to the corresponding system.

Here is a video walk through:

Configure Connection Settings

Now that we have the Integration Packs registered and deployed, we still need to provide connection information so that Orchestrator will be able to communicate and operation with these other systems.

Open Runbook Designer, select Options from the menu, and select the system you want to configure connection settings for. In this example, we will use ‘SC 2012 Configuration Manager’.

Connection Settings 01

When the Connections dialog appears, click the Add button.

Connection Settings 02

On the Connection Entry screen, provide a name (to identify the connection), and fill in the Server, Username, and Password to use for the connection. In a Production environment, a dedicated Service Account would be created/used for each product connection. Don’t forget to test the connection to ensure it can communicate with the system you are integrating. Then press OK.

Connection Settings 03

Connection Settings 04

The newly added connection will be shown. Click Finish.

Connection Settings 05

If you have more than one Integration Pack, you will have to configure the connections for each of them.

IMPORTANT: If you are trying to configure the System Center Integration Pack(s), you will need to install the console(s) for the product you are integrating (i.e. SCOM, SCCM, etc.); else, you will get an error when testing the SCORCH connection.

Here is a video walk through: