Orchestrator System Center Integrations Part 1 – Setting up the Integration Packs

One of the common things we see as consultants is that organizations implement one System Center product because that is what they know use daily. However, if your company purchased System Center 2012, you own System Center Orchestrator; but are you using it? System Center Orchestrator is a complete IT automation solution for your Datacenters.

In Part 1 of this Blog on Orchestrator, I am going to go over the setting up the Integrations between Active Directory, Operations Manager, Configuration Manager and Virtual Machine Manager. In Part 2 we will create a simple Runbook that creates a computer account in a specific OU. In Part 3, diving in a little more, we will add onto the Runbook by creating the a virtual machine that we created the computer account for in AD. In Part 4, we will add in Alerts for the build process of the VM into Operations Manager. Then finally, in part 5, I will throw out there the Runbook that everyone wants; a simple way to place computers into Maintenance Mode in OpsMgr based on a Configuration Manager Collection.

The goal of this blog series to get you, the admin fighting fires every day, to start simplifying your life by using Orchestrator to do the hard work. All the examples given in this 5 part blog post are easy to setup and configure. With a little practice you can begin to start developing your own ideas on how you want to automate you work loads so you can get home at a decent hour each evening or just spend the day yappin and show your boss how much work you accomplished Smile.

At MMS 2013, Catapult Systems MVP’s – Cameron Fuller, Chris Ross, and Jason Sandys (along with Carl played by Mike Vrabel on the Helpdesk) presented on Provisioning with System Center 2012, which can be seen here: http://channel9.msdn.com/Events/MMS/2013/IM-B317

The Runbook we are going to create in this series is what was used for the demonstrated during the part when the guys demonstrated provisioning a computer using System Center Service Manager based on a template in VMM. The last Runbook, I created one evening for a customer that wanted to place computers into Maintenance Mode based on a Collection in Configuration Manager for their monthly system patching.

Alrighty then, enough with the yappin… let’s get going…

Setting up the Integration Packs

After you install Orchestrator, the next thing you need to do is install the Integrations Packs for System Center 2012 SP1. Installing the Integration Packs is a two part process using the Orchestrator Deployment Manager; first you Register the Integration Pack, then you deploy the Integration Pack to your Orchestrator Server.


More information on this process can be found on TechNet here:


As you can see, I have in my lab the IP’s for AD, ConfigMgr, OpsMgr and VMM deployed to my lab Orchestrator Server; along with a few others.


Now let’s setup the Integrations starting with AD. In the Runbook Designer, select Options, Active Directory.


When the Prerequisite Configuration comes up, select Add… to add in a new Configuration. Also note that you can add additional configuration if you want; you are not limited to having only one configuration. Give you configuration a Name and select the ellipse and select “Microsoft Active Directory Domain Configuration” and click OK


In the properties for Active Directory, enter in an account that has write access into Active Directory. You can also use a delegated account and set a Default Parent Container. My ORRunAs account is a Domain Admin for my lab so I just leave the Default Parent Container blank. That’s about it for the AD configuration; click OK, then Finish, you’re done.


Moving on, let’s setup the Connections to Configuration Manager. Following the same process as with AD, I select Add… then I only need to enter in a Name for the connection, my ConfigMgr Sever name, an account and password, then test the Connection. I could have used the ORRunAs account except it is not a ConfigMgr admin in my lab so I just used my lab account.


Now let’s now setup the connection to Operation Manger. Selecting Options again, click on SC 2012 Operations Manager. Enter in a name for the Connection, the Server name to the RMSe server, domain, user name and password. Then Test the connection.


Now let’s setup Virtual Machine Manager. Notice that we have a Prerequisite Configuration as with AD. Same as the others, enter in the VMM Server name, User, Domain, and password. Since I have not changed any of the ports in my lab, nor the authentication Type, I leave defaults. The last thing I want to enter is the where the VMM Administrator Console is located. If you installed the console on the Orchestrator Server, as you have to do with Operations Manager, then you would enter in local host. In SP1 you no longer need to install the console locally. I just enter in the name of my VMM server. If you installed VMM on Core, you may want to install the console on the Orchestrator server. Up to you for your environment. There is not test button for VMM nor for AD. Maybe future IP’s for System Center will include it. To test, just select and activity and see if you get any errors. More on this later.


So now we have setup our Integration Packs. Now we will see if the Active Directory integration is working. In Part 2 of this blog series on Orchestrator, we will create Runbook with two activities to create a computer account in a specific OU in AD.