create incident create checkpoint start maint mode shut down vm e-mail on error update on success...
TRANSCRIPT
Runbook Design 101
Jakob Gottlieb Svendsen
DCIM-B375
Jakob Gottlieb Svendsen – @JakobGSvendsenProfession
Chief Developer, Coretech A/S, System Center Gold Partner
TitlesSystem Center Cloud and Data Center Management MVPWindows Azure Pack / SMAOrchestrator + Extensions for SCSM + SCOMVBScript / PowerShell / VB.NET / C#.NET
CommunitiesCo-Founder of the Danish PowerShell User Group (www.psug.dk)Moderator on Microsoft TechNet Forums
AuthorService Manager 2012 Unleashed (contributing author – Release 2014)Mastering System Center Orchestrator 2012 – 3 day workshopWindows Azure Pack – SMA Workshop/course (in development)Advanced SCOM management pack design/development Workshop/course (in development)
Who am I
Introduction to OrchestratorRunbook PlanningRunbook DesignBest PracticesLoggingStage Tracking
Agenda
Introduction
Orchestrator Concepts
Create Incident Create Checkpoint Start Maint Mode Shut Down VM
E-mail on error Update on success
Invoke Web Services
Compare Values
Send e-mail
Query Database
Run .NetScript
Clone Linux VM
Return Data
Check Schedule
Activities Runbooks Databus
Executes a task Collection of Activities Published Data from Activities
Get Data Source Create Recovery Point UpdateService Request
Solution or Application specificProvide ready-built defined activitiesPackaged and DeployedBrings version control to activities
Microsoft and Partner providedAll major enterprise management productsHP, IBM, CA, BMC, EMC
Build your own with the Integration Toolkit!Leverage the Community ecosystem
Integration Packs
Example - Deploy Web site
Create Folder Copy Content Create Web Site Test Web Site
DemoBasic runbook
Jakob Gottlieb Svendsen
Runbook Planning
When to Automate Activities ?
Easy to Automate Occurs Often
Visible to Customers High Risk Breaches SLA
Often
Time Consuming
Is the process optimized and standardized?Is SCO the right tool?Ports & Permissions?Development Cost vs. Manual Process
Identify the best processes
Automate “manual” task1 time every monthTakes 20 minutes to do 1 week to build runbook
Scenario 1 – Basic Task
Scenario 1 – Basic Task
0 1 2 3 4 5 6 7 8 9 100
5
10
15
20
25
30
35
40
45
4 Hours
37.5 Hours
Year
Hours
Automate “Service Stopped” alerts1 alert every day1st line receives and forward (5 mins)2nd line RDP and fix (15 mins)1 week to build runbook
Scenario 2 – Incident Remediation
Scenario 2 – Incident Remediation
0 1 2 3 4 5 6 7 8 9 100
200
400
600
800
1000
1200
1400
122 Hours
1217 Hours
37.5 Hours 37.5 Hours
Year
Hours
Invent “Skynet”The runbook will monitor this system for new objects, then it will… then it will integrate with… and pass data into……We don’t think it will take more than 14-18 months to build the solution. …By the way, we have never used Orchestrator before
Customer Request / Dream
Runbook Design
DemoDesign Guide
Jakob Gottlieb Svendsen
Design GuideRename activitiesUse link labels & colors
SuccessWarning / Failed“Could be”
Left to right
Folder and runbook structureNaming conventionVariablesLibrary of standard runbooks
DemoWatch Out!
Jakob Gottlieb Svendsen
Success might not equal to your expectationNo Loops in Links – Only on activity levelMultiple Results (Multi-value published data)Library runbooks might be in use!
Watch Out!
Does one taskEasier to develop and testCan be used in multiple scenariosDo not use when handling a lot of executions
Adds a delay of a couple of seconds per execution.
Build Modules
DemoModules
Jakob Gottlieb Svendsen
Logging
Text FileEvent log
Except SCOM monitors
Platform EventBuilt-in “Activity Specific Logging”
Custom DatabaseIP for Standard Logging SCSM – Action Log Own IP using the Wizard
Don’ts Do’s
DemoLogging
Jakob Gottlieb Svendsen
InfrastructureMultiple Runbook Servers
RunbookDesign to support failoverResume at the correct stage (staging)
Fail-Over
Runbook Servers
Data Store
Integration Pack for Standard LoggingCustom DatabaseService Manager
State Tracking
DemoState Tracking
Jakob Gottlieb Svendsen
Windows Server 2012 R2 SupportService Management Automation
Windows Azure PackRunbook WorkersPowerShell based Runbooks
System Center Integration Pack for Microsoft SharePointBug fixes
System Center Orchestrator R2
Use Run .Net Script ActivityUse Smart for Runbook Conversion
Get it at TechNet Galleryhttp://gallery.technet.microsoft.com/SMART-SMA-Runbook-Toolkit-1b53d532
Design for ”easy” SMA Migration
Start small / simple
Planning makes development much faster!
Use Service Manager for staging support
Summary
Breakout / Theatre
Theater Presentation – SCCM & Orchestrator – ”Magic is in the glue” – Wednesday 12:30-12:50
DCIM-B411 Datacenter Integration Using Service Management Automation in Microsoft System Center 2012 R2 Orchestrator
Related content
Labs
DCIM-H303 Microsoft System Center 2012 R2 Lab 3: Automation & Self-Service
DCIM-H313 Microsoft System Center 2012 R2 Lab 4: IT Service Management
DCIM-H311 Automating Your Daily Tasks with Windows PowerShell
Come Visit Us in the Microsoft Solutions Experience!
Look for Datacenter and Infrastructure ManagementTechExpo Level 1 Hall CD
For More InformationWindows Server 2012 R2http://technet.microsoft.com/en-US/evalcenter/dn205286
Windows Server
Microsoft Azure
Microsoft Azurehttp://azure.microsoft.com/en-us/
System Center
System Center 2012 R2http://technet.microsoft.com/en-US/evalcenter/dn205295
Azure PackAzure Packhttp://www.microsoft.com/en-us/server-cloud/products/windows-azure-pack
Resources
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
msdn
Resources for Developers
http://microsoft.com/msdn
TechNet
Resources for IT Professionals
http://microsoft.com/technet
Sessions on Demand
http://channel9.msdn.com/Events/TechEd
Complete an evaluation and enter to win!
Evaluate this session
Scan this QR code to evaluate this session.
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.