from Microsoft MVP Roadshow 2015 - Copenhagen

1. Jakob Gottlieb Svendsen
System Center Orchestrator
Service Management Automation
Automating System Center 2012 R2
@JakobGSvendsen
http://blog.coretech.dk/jgs/

2. Who am I
• Chief Developer / Consultant / Trainer
• Coretech A/S, System Center Gold Partner
– Offices in
• Titles
– System Center Cloud and Data Center Management MVP
– Member of the System Center Influencers Team
• Areas
– Orchestrator / Service Management Automation / Windows Azure
Pack
– Extensions for System Center (PS,VB.NET,C#.NET)
• Communities
– Co-Founder of the Danish PowerShell User Group (www.psug.dk)
• Author / Training
– Service Manager 2012 Unleashed (contributing author – Released
October 2014)
– Mastering System Center Orchestrator 2012 – 3 day workshop
– Service Management Automation - 3 day Workshop (New!)

3. Agenda
• Short Introduction
• Scenario: Azure Pack Integration
• Scenario: SCCM/Intune – Monitor Jailbreaks
• Monitors in SMA
• Scenario: SCOM/SCVMM – Extend VM Drive
• SCOM – Using Recovery Action
• Scenario: SCSM/SCCM – Import Computer(s)

4. Core
Resource
clouds
Automation Billing Tenant
management
Hosting
plan
Hardware
IaaS
Virtual
machines
PaaS
Service
bus
PaaS
Websites
IaaS
Network
PaaS
DatabaseAzure Pack Operations Manager
Infrastructure& application
monitoring,alerting& usage
Data Protection Manager
Continuousprotectionof key
applications& workloads
Service Manager
IT servicemanagement&
requestauthoring
Orchestrator
Integration& automationof key
technologies& processeswith
SMA & Service Manager
Virtual Machine Manager
Fabric,library& cloud management
Service Delivery stack

5. Service Management Automation (SMA)
• System Center 2012 R2 Orchestrator adds support for
PowerShell Workflows through the SMA feature
• Browser-based runbook authoring integrated into the Azure Pack Portal
• Supports requirements for scale and high availability
• Import PS modules and create additional modules and runbooks
• Check out the Building Clouds Blog for an Introduction to SMA
http://aka.ms/IntroToSMA

6. Demo
Introduction

7. SCOM CI Connector
Service
Manager
Operations
Manager
Monitored
Instances
Operations Manager CI Connector
Any Monitored Resources
*nix / bsd
Network
Custom classes
Import All MPs from Operations
Manager to Service Manager
OPTIONS

8. • GridPro
– Designed the same way as the original Out-Of-The-Box Orchestrator connector
– Strict relationship runbook and template, using SMA runbook templates
– Self Service Integration into Windows Azure Pack Gallery with GridPro Request
Management
• Cireson
– Works is a more flexible – less strict way
– Workflow event subscription
– Stand alone Self service portal
Contact Coretech / Me for more info / purchase

9. Scenario: SCCM/Intune – Monitor Jailbreaks
Microsoft Intune
Mobile devices

10. Building PowerShell Monitors
• Monitor using a loop (While)
• Check the target (New alerts
etc.)
• Trigger Action
• Sleep for x seconds

11. Building PowerShell Monitors - Refresh
• Refresh Monitor every once in a while
– Depends on purpose and output size of runbook
• 24 hours, 1 hour, 20 minutes etc.
– Loop until refresh time
– Restart runbook using web service
• Use $WorkFlowCommandName

12. SCCM/Intune – Monitor Jailbreaks – Extension
• Day 1: Warn User
• Day 3: Block User (Mail etc.)
• Day 7: Wipe Phone!
• 2nd time…..
Get-Employee | Remove-Employee
New-Employee

13. SCOM – SMA Monitor

14. Scenario: SCOM/SCVMM – Extend VM Drive

15. Demo
SCOM/SCVMM
Extend VM Drive
Basic – Using Resolution State

16. Building PowerShell Monitors - Query
• Limit Query to minimum
– “Mark” the objects
• SCOM Alert – Resolution State
– Use last search date/time
• SCOM Alert – TimeRaised
• Active Directory – WhenChanged
• NOTICE – Assets are Universal Time!

17. Demo
SCOM/SCVMM
Extend VM Drive
Optimized Query

18. Monitors – Not too many
• Try not to get too many Monitors
connecting to the same system
– Consolidate Monitors into one
– Use other techniques to trigger the runbook
• SCSM – Workflows
• SCOM - Recovery Action

19. SCOM – Using Recovery Action

20. Demo
SCOM/SCVMM
Extend VM Drive
Recovery Action

21. SCOM/SCVMM – Extend VM Drive - Extension
• The source of the alert/problem is not fixed!
• Make sure you monitor when this happens
– SCSM – Incidents
– Reports

22. Did I Cheat??
Just a little bit!
Logical disk space check interval was 5 seconds
Compared to every 15 minutes by default.

23. Scenario: SCSM/SCCM – Import Computer(s)

24. Mac Address Barcode
• Some manufacturers add
extra text
• Needs to be removed
before import
This manufacturer adds “23S”

25. Demo
SCSM/SCCM
Import Computer(s)

26. SCSM –> SMA Connectors
• GridPro
– Designed the same way as the original Out-Of-The-Box Orchestrator
connector
– Strict relationship runbook and template, using SMA runbook templates
– Self Service Integration into Windows Azure Pack Gallery with GridPro
Request Management
• Cireson
– Works is a more flexible – less strict way
– Workflow event subscription
– Stand alone Self service portal

27. SCSM/SCCM – Import Computer(s) –Extension
• Import List of Computers
– Submit a CSV File via Form
• Add other properties
– Primary User (SCSM/SCCM)
– Serial Number etc.
• Cireson Assset Management
– Create Hardware Asset
– Contact Coretech!

28. Best Practice
• Modularity! Modularity! Modularity!
• Example:
Keep Monitor, Check and Fix
in seperate runbooks
for simplicity and easy testing

29. Best Practice
• One Monitor + Multiple Actions on
different results
• Example:
– One Monitor for all SCOM Alerts.
– One ”Dispatcher” runbook to execute an
action based on alert details

30. Best Practice
• Error Handling!
• Use Try / Catch

31. Links
• My Blog
http://blog.coretech.dk/jgs’
• Building Clouds Blog
http://blogs.technet.com/b/privatecloud/
• Tips & Tricks Wiki – Ryan Andorfer
http://social.technet.microsoft.com/wiki/contents/articles/26616.quick-tips-
and-tricks-for-runbook-writing.aspx