Introduction Service Management Automation Windows Masters Event Introduction Service Management Automation Dennis de Roo

Agenda SMA? SMA architecture Comparison Installation and configuration Runbook Authoring Automation Roadmap

What is SMA? SMA=Service Management Automation Process automation tool An automation engine based on PowerShell workflows The Microsoft automation stack currently contains three products Orchestrator – Software acquired in 2011 that assists with graphical automation Service Management Automation (SMA) – Software developed in house for automation Azure Automation – Automation delivered in public azure (and on prem via hybrid automation runbook workers possible via Operational Insights)

Overview Automation PowerShell Scripts Workflows Desired State Configuration (DSC) System Center Orchestrator (SCORCH) Service Management Automation (SMA) The “new” Orchestrator Azure Automation (AA) Automation as a Service

Architecture WAP Optional layer Web Service PowerShell Module HTTP Request Authoring Debugging Operating Optional layer HTTP Response Web Service Results PowerShell Module Runbook service PowerShell Modules REST oData web service Authorizes users Runbooks Jobs Modules Submit requests Runbooks Runbook Resources Tracks runbook job state Pickup Jobs SMA Database Runbook Workers

SMA and the Windows Azure Pack WAP provides an GUI to SMA Native connector between WAP actions and SMA automation WAP is not necessarily necessary for SMA to function No Administration capability from the Wap Tenant Portal

SMA vs Azure Automation Private Cloud Public Cloud These are essentially the same, the only difference being the location from which they are delivered IT Pro IT Pro Service Management Automation Microsoft Azure Automation

Management (SMA vs Azure Automation) IT Pro IT Pro SMA Portal WAP SMA Powershell Module Azure Management Portal Azure Powershell Module REST Service Azure Automation Service

SMA vs Orchestrator SMA Orchestrator 64 bit 32 bit Own infrastructure Integration via PowerShell modules Integration via Integration Packs Authoring via WAP or PowerShell ISE Authoring via Runbook designer Unlimited job concurrency per runbook worker Job concurrency of max 50 instances per runbook server Interact with Rest Web service

SMA integrate solution with TFS https://blogs.technet.microsoft.com/privatecloud/2014/05/08/automationmvp-spotlight-seriestfs-and-service-management-automation-better-together/

PowerShell Workflow Introduced with PowerShell 3.0 Code looks like a function Executed by Windows Workflow Foundation engine (WWF) Benefits to PS Workflow Checkpoint / Suspend Parallel execution across one or more systems Well suited for long running tasks *Native Litmited CMDLET Support (CMDLET Support use = inline script)

PowerShell Workflow code Parameter Block Assets Inline Script

Administration, Authoring and Execution WAP Portal or PowerShell ISE Runbook Tags for organization Potential Runbook states (Draft, Published, In –Edit) Flexible execution methods Job = instance of executed Runbook

SMA Powershell module Provides 40 cmdlets to remotely manage SMA from any host Talks to SMA web service Separate install in the SMA installer Comes out of box as an SMA integration module for use in runbooks Cmdlets for SMA administration: - Runbook Worker Deployments - Administration Settings - Product License / Expiration Date

SMA Powershell module import-module Microsoft.SystemCenter.ServiceManagementAutomation Get SMA Runbooks using standard parameters Get-SmaRunbook -WebServiceEndpoint "https://ac-sma-0001.service.asapcloud.nl" -Port 9090 Start SMA Runbook using Name $connection = @{"WebServiceEndpoint"=" https://ac-sma-0001.service.asapcloud.nl ";"Port"=9090} Get-SmaRunbook @connection -RunbookName "My SMA Runbook" | Start-SmaRunbook @connection Create new Schedule $StartDate = Get-Date $EndDate = Get-Date -Day 12 -Month 6 -Year 2023 Set-SmaSchedule -StartTime $StartDate -ExpiryTime $EndDate -Name "Schedule01" -ScheduleType "DailySchedule"

Demo Introduction

Installation & configuration

Post Deployment Deploy SMA Components Deploy multiple Runbook workers Deploy WAP (optional) Configure WAP integration (optional)

Deployment Production Environment Multiple Runbook Workers for load distribution and HA Web services load balanced SMA Admin portal load balanced SQL AlwaysOn Cluster SMA Portal WAP SMA Portal WAP SMA Webservice & Runbook Worker SMA Webservice & Runbook Worker Always ON Always ON

Assets Assets: globally available combination of settings Connections – connection information for external systems Variable – available to all Runbooks Credentials – PSCredential or Certificate Schedules – Runbook execution schedule

CheckPoint / Suspend Checkpoint: Snapshot of current state Checkpoint-Workflow -PSPersist $True placed after activity $PSPersistPreference = $True Suspend-Workflow Suspend: Pause Runbook job Suspend-Workflow: Checkpoint and Suspend Suspend-SmaJob: Suspend at next checkpoint WAP UI: Suspend at next checkpoint Workflow exception/Runbook worker crash

Nesting Runbooks Invoke Inline: starting a runbook by name Parent and all nested compiled into one job Output of all runbooks will be ‘rolled up’ Synchronous execution Start-SmaRunbook: starting using PS CmdLet Starts a second job Output is specific to each job Asynchronous execution

Inline Script Execute true PowerShell within workflow Creates PowerShell session returning output to workflow Check Point/Suspend not valid Workflow variables are not visible to inline script $Using scope modifier (Example $Using:ComputerName)

Demo Runbooks

Transition Orchestrator -> SMA Get rid of Orchestrator IPs / Native Actions Use generic .NET (PS) Script actions Integrate both worlds to save existing investments

Things you should avoid Code first plan after Creating a single, giant runbook Using hardcoded values Installing native consoles and tools on workers

Automation Roadmap for SC 2016 System Center Orchestrator Service Management Automation (with) Windows Azure Pack OMS Automation Will be shipped in SC 2016 Updating Integration Packs to support latest System Center components Continue to get Update Rollups and Hot fixes Continue to make feature enhancements Migration tools available to carry forward your SCO investments Add on to System Center Monthly releases with new capabilities On-demand hotfixes anytime

Notes SMA is the future of automation Rollbacks, Failover, Scalability are there OOB PowerShell open endless possibilities

Thanks!