System Center 2012 R2 Orchestrator

1. System Center 2012 Orchestrator R2
Northwest System Center User Group
May 9th 2014
Identity Management | Data Protection | Extended Enterprise
© 2014 Edgile, Inc. – All Rights Reserved

2. © 2013 Edgile, Inc. – All Rights Reserved
Enterprise Automation

3. © 2013 Edgile, Inc. – All Rights Reserved
System Center 2012 – Cloud OS
Azure
Integration
Pack

4. © 2013 Edgile, Inc. – All Rights Reserved
Deploy Services Automatically

5. © 2013 Edgile, Inc. – All Rights Reserved
Automating Self-Service
User requests
Provisioning
Release
management
Rapid change
Customers face resource and management challenges
with too many manual processes and efforts
Application Deployments
SLA adherence
Capacity management
Manual tasks
Batch scripts
Patch remediation
Automating self-service results in
lower management overhead and
focused scarce resources
Reduce manual admin
efforts for routine tasks
Decrease in
errors and
rework
Empower application owners
to deploy applications and services
consistently and reliably
Give users fast and
easy access to
services

6. © 2013 Edgile, Inc. – All Rights Reserved
Orchestrator Overview

7. © 2013 Edgile, Inc. – All Rights Reserved
Automation Concepts

8. © 2013 Edgile, Inc. – All Rights Reserved
Tiny Demo
8

9. © 2013 Edgile, Inc. – All Rights Reserved
Process
automation
Service Delivery and Automation
Architecture
Integration
Orchestrator
Automation

10. © 2013 Edgile, Inc. – All Rights Reserved
Automation Best Practice Planning
10
Develop a Runbook Automation Wish List
• Which processes are the most time-consuming?
• Where are service levels suffering the most?
• Which problems recur most frequently?
• Which are most expensive for the company?
• Which process failures are visible to everyone?

11. © 2013 Edgile, Inc. – All Rights Reserved
Automation Best Practice Planning
11
Identify Best Candidate Processes for Runbook
Automation
• Is Orchestrator the right tool for this task?
• Is it technically feasible?
• Development cost and effort?
• Time to recoup investment
• What ports and permissions will this use?
• Closing the loop with ITSM integration

12. © 2013 Edgile, Inc. – All Rights Reserved
Automation Reality Funnel
12
Identify Best Candidate Processes for Runbook
Automation
Best candidates for runbook
automation
Recovery
Tasks
Incident
Remediation
User
Provisioning

13. © 2013 Edgile, Inc. – All Rights Reserved
Scenario 1 – Basic Task Automation
13
Automate “Manual” Tasks
Occurs 1 time every month
Takes about 20 minutes to complete
Estimate: 1 week to build Runbook
20 minutes x 12 months = 4 hours per year
40 hours / 4 hours = 10 years ROI

14. © 2013 Edgile, Inc. – All Rights Reserved
Scenario 2 – Incident Remediation
14
Automate “Service Stopped” Alerts
1 Alert Every Day
1st line Help Desk receives and forward (5 mins)
2nd line remediates and fixes (15 mins)
Estimate: 1 week to build Runbook
20 minutes x 365 days = 121 hours per year
40 hours / 20 minutes = 120 days = 4 months ROI

15. © 2013 Edgile, Inc. – All Rights Reserved
Remember – You Can Make it Worse!
15