Orchestrator 2012
The Unknown Hero of Automation
David Norling-Christensen
Senior Systems Architect
A Brief Introduction to Orchestrator
 So what is Orchestrator?
 A visual scripting tool to automate repetitive tasks.
 “Orchestrator is a workflow management solution for the data center.
Orchestrator lets you automate the creation, monitoring, and
deployment of resources in your environment.” (From Microsoft
TechNet)
A Brief Introduction to Orchestrator
 Primary Functionality
 Runbooks – Visual Scripts to do an activity.
 Runbook Server – Server to run Runbooks.
 Orchestrator Console – Web interface to run and monitor Runbooks.
A Brief Introduction to Orchestrator
 Runbook Native Functionality
 Interact with Event Logs
 Interact with WIM
 Interact with SNMP
 Interact with Services
 Monitor Date/Time
 Interact with Files
 Send Email
 Interact with Database (Access, ODBC, Oracle, SQL Server)
 Text File Manipulation
A Brief Introduction to Orchestrator
 Downloadable Integration Packs
 Active Directory Integration Pack
 HP iLO and OA Integration Pack
 HP Operations Manager Integration Pack
 HP Service Manager Integration Pack
 IBM Tivoli Netcool/OMNIbus Integration Pack
 VMware vSphere Integration Pack
 Configuration Manager 2007/2012
 Data Protection Manager 2010/2012
 Operations Manager 2007 R2/2012
 Service Manager 2010/2012
 Virtual Machine Manager 2008 R2/2012
A Brief Introduction to Orchestrator
 Integration Pack Advice
 Follow the TechNet Articles for each Integration Pack to ensure that it
is configured correctly for your environment.
Orchestrator Demo




Runbook Designer Overview
Runbook Tester Overview
Orchestrator Console Overview
Deployment Manager Overview
Orchestrator Demo
 Orchestrator Scripting 101
 Initialize or Monitor
 Actions
 Connectors
 Subscribed Data
 Reporting
Orchestrator Demo
 Issue
 Applications in System Center Configuration Manager 2012
Application Catalog that require management approval create an
entry in the Configuration Manager Console. Someone would have to
look at this location to know that a request is pending.
 Possible Solutions?
 Runbook Solution Demonstration: Approval Email
Orchestrator Demo
 Issue
 You need to delete a computer from your environment, however the
computer is in multiple systems (AD, SCCM, etc…)
 Possible Solutions?
 Runbook Solution Demonstration: Delete Computer
 Simple Change for Users instead of Computers
Orchestrator Demo
 Issue
 Computers leave your environment and are not properly removed
from the required system. This leaves inactive computers in multiple
systems.
 Possible Solutions?
 Runbook Solution Demonstration: Inactive Computers
 Simple Change for Users instead of Computers
 Could easily call Delete Computer runbook at the end of this runbook
Orchestrator Demo
 Issue
 Critical VM’s get shutdown either via an issue or because of user
actions.
 Possible Solutions?
 Runbook Solution Demonstration: Verify Critical VMs
 Could easily start the VM as an action as well
Orchestrator Demo
 Issue
 VM’s with dynamic VHDs take more HD space than needed as users
user them
 Possible Solutions?
 Runbook Solution Demonstration: Shrink Disks
Orchestrator Demo
 Issue
 Users need local admin rights on their VMs via their domain account
 Possible Solutions?
 Runbook Solution Demonstration: VM Local Admin
 Limits this to run against VM’s and only the owner of the VM only gets admin
rights.
A Brief Introduction to Orchestrator
 What Can it Do Well
 Automation of repetitive tasks
 Evaluation a large amount of data and take action based on criteria
A Brief Introduction to Orchestrator
 Better Together (other system center)
 Service Manager as starting point
Orchestrator Implementation
 Single Computer Design
 Less than 50 running Runbooks at a given time.
 Can not be installed on a Domain Controller
 Hardware Requirements
 1 GB of RAM (2+ recommended)
 200 MB of HD Space
 Dual Core 2.1 GHz or better processor
 Software Requirements
 Server 2008 R2 / Server 2012 (SP1 Beta)
 SQL Server 2008 R2 / SQL Server 2012 (SP1 Beta)
 Database Engine Services only
 IIS (Orchestrator install will enable for you)
 Microsoft .NET Framework 3.5 SP1 (Orchestrator install will enable for you)
 Microsoft .NET Framework 4
 Silverlight 4 (Any computer that uses the Orchestrator Console)
Orchestrator Deployment Manager
 Used to install Integration Packs
 Used to push the Runbook Designer (and Integration Packs)
 Software Requirements:
 .NET 3.5 Installed
 System Center integration packs require
 WiX 3.5 (NOT 3.6)
 Orchestrator Toolkit (Found with Integration Packs, plus reboot after)
Orchestrator Design Principles
 Keep it simple
 Keep it modular
 Keep it scalable
Orchestrator Discussion
 Open floor for your issues?
Call to Action
 Let Bennett Adelson help you evaluate your current System
Center setup and identify how Orchestrator can best help
you.
 Discuss your current and future System Center environment
 Help educate and inform on System Center capabilities
 Help identify System Center quick wins for your organization and
create a roadmap to help you reach your goals!
Orchestrator 2012
“The Unknown Hero of Automation”
Information
Worker
Solutions
User
Exerience
Other Events:
Visual Studio Roadshow
Cleveland Microsoft Office
October 23rd
Microsoft Hybrid Cloud OS Launch
Cleveland Microsoft Office
November 6th
System Center Roadshow Columbus
Microsoft Office
November 14th
Advanced Infrastructure
Member of Partner Advisory Council for Software + Services
MESSAGING &
COLLABORATION
Preferred Deployment Partner for Office365
Email
Executed one of the largest Lotus Notes to BPOS-S
migrations to date
Portal
Unified Communications
Microsoft Online Services
Charter Member – Cloud Kit Migration Expert
Dedicated Migration Swat Teams
Windows 7 Jumpstart Partner
Founder, Cleveland System
Center User Group
OPERATIONS
MANAGEMENT
System & Software
Deployment
Patch Management
Monitoring and Reporting
Backup & Disaster Recovery
Virtualization & Storage
ARCHITECTURE
Identify and Directory
Services
Web Platforms
Network and Security
Shared Services
Thank you from Bennett Adelson
Follow Us:
Twitter - @bennett_adelson
Blog - http://bennettadelson.wordpress.com/
Website – www.bennettadelson.com
Contact Us:
Andrew Thorne – Sales Coordinator
athorne@bennettadelson.com
Phone: (419)515-9217
David Norling-Christensen – Senior Consultant
dnorling-christensen@bennettadelson.com
Phone: (847)769-4459
Jarrod Roark – Director of Advanced Infrastructure
jroark@bennettadelson.com
Phone: (614)738-4519
Migrate
Plan
Build
Optimize
Deploy