You can download integration packs from the Internet, import them using the System Center 2012 R2 Orchestrator Deployment Manager as shown in Figure 1-1, and then deploy them to your runbook servers.įIGURE 1-1 Orchestrator integration packsĪn Orchestrator deployment consists of the following parts: An integration pack is a collection of product-specific tasks that you can trigger through Orchestrator. Orchestrator can still call Windows PowerShell scripts, but it also integrates with many other products, including products within the System Center suite through integration packs. Unlike Windows PowerShell, which requires you to write scripts using an editor like Windows PowerShell ISE, Orchestrator allows you to build automation using a drag and drop interface called the Runbook Designer. The System Center product that you use to create runbook automation is System Center 2012 R2 Orchestrator. Runbook automation is important in Microsoft private cloud environments because it allows you to automate complex tasks. Today runbooks are software parts that, when triggered, actually perform the procedures with little or minimal direct input from the server administrator. These books contained documentation that described to the server administrator how to perform specific procedures.

Originally, runbooks were actual physical books. Runbooks represent a set of procedures that a server administrator performs on a regular basis. With runbook automation you can automate complicated workflows. Change and activity management workflows.This section covers the following topics:

Microsoft system center