Simple play icon Course
Skills Expanded

System Center Orchestrator 2012 R2 Fundamentals

by Kunal D Mehta

Learn the basics of IT process automation in the datacenter using System Center Orchestrator 2012 R2.

What you'll learn

This is a beginner level course focusing on the automation engine of the System Center suite: Orchestrator 2012 R2. Here, we'll learn about the product architecture, deploy the product, create runbooks to automate day-to-day IT processes, extend its functionality using integration packs, learn about the basic design principles and recommendations, improve performance by optimizing the setup, and prepare for high-availability and scalability.

Table of contents

Course FAQ

What is System Center Orchestrator 2012 R2?

Orchestrator comes as a part of the well-known datacenter and client management toolkit, the System Center suite. Orchestrator is a visual, non-scripting- and no-coding-based solution that offers activities you can drag-and-drop onto the workspace and connect them through links to create the desired workflows.

What are runbooks?

In a computer system or network, a runbook is a compilation of routine procedures and operations that the system administrator or operator carries out. System administrators in IT departments and NOCs use runbooks as a reference. Runbooks can be in either electronic or in physical book form.

What are integration packs?

The integration pack for Operations Manager is an add-in provided by System Center Orchestrator. Use the integration pack to connect an Orchestrator Runbook server to an Operations Manager management server so you can automate various actions.

What is IT Process Automation?

IT process automation facilitates the orchestration and integration of tools, people and processes through automated workflows. ITPA software applications can be programmed to perform any repeatable pattern, task or business workflow that was once handled manually by humans.

How do you create a runbook?

Every runbook is unique and specific. The actual content will be specific to your needs. The methodology, however, is the same as it is for all process creation. The first stage is to plan which procedures need to be documented in your runbook. When you have a list, you can write them up in detail. After field testing a process, you can make updates and optimizations as necessary.

About the author

Kunal D Mehta is a Microsoft and VMware certified IT Pro specializing in Core Infrastructure solutions like Windows Server, Active Directory, Exchange, SharePoint, Office 365, Azure, and System Center products. He has trained about half a dozen SI partner companies in India on Server 2012 and Private Cloud solutions covering over two thousand people. When he is not doing his geeky thing, he likes to hang out with friends to play a game of snooker or bowling. He also loves watching all types of m... more

Ready to upskill? Get started