System Center 2012 R2 Windows Azure Pack Service Management Automation 101

Who am I Jakob Gottlieb Svendsen Profession Chief Developer, Coretech A/S, System Center Gold Partner Titles System Center Cloud and Data Center Management MVP Windows Azure Pack / SMA Orchestrator + Extensions for SCSM + SCOM VBScript / PowerShell / VB.NET / C#.NET Communities Co-Founder of the Danish PowerShell User Group ( Moderator on Microsoft TechNet Forums Author Service Manager 2012 Unleashed (contributing author – Release June 2014) Mastering System Center Orchestrator 2012 – 3 day workshop Windows Azure Pack - SMA Workshop/course (in development) Advanced SCOM management pack design/development Workshop/course (in development)

Use cases for process automation /privatecloud/archive/2013 /10/29/ aspx AreaExample Alert Triage and RemediationAutomating tier 1 monitoring activities (diagnostics and recoveries) Maintenance TasksCluster patching Stop/start servers or services in the right sequence Automate SQL Server maintenance tasks Maintenance windows Service Catalog, Provisioning and Change Management Automation Automate all or part of change management activities Server and VM provisioning Integration with a service catalog Dynamic Resource Allocatione.g. depending on load or calendar Cross-Technology IntegrationConsistently integrate ticketing in processes Migration and interoperability between different solutions (e.g. new monitoring or ticketing system) Line of Business ScenariosNew employee onboarding, password resets, file transfers, etc.

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 WAP Admin 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

Service Management Automation Introduction Demo

Introducing PowerShell Workflows  Workflows are a PS construct similar to a function or cmdlet  Converted to and executed as a Windows Workflow Foundation workflow  Workflows are different from a function/script/cmdlet  Workflows can execute commands in parallel or in sequence  Workflows can persist state  You can suspend/resume a workflow  Workflows “survive” OS shutdowns or network outages  Runs activities. Cmdlets are run inside of an InlineScript block

Service Management Automation First runbook Demo

SMA enhancements to PowerShell Workflow  High availability workflow execution backed by SQL Server  Centralized, machine-independent store  Variables, Credentials, Connections, Certificates  Schedules, Actions (Trigger on Events)  Modules, Workflows, Checkpoints  Built-in versioning for workflows and modules  API interface over HTTP (Odata web service)  Historical view of all workflow jobs and their output

Service Management Automation Triggers + Schedules Demo

SMA : Architecture and Installation Web Service Standard interface for all of SMA Security group controls access HTTPS support to secure connection to clients Runbook Worker All runbook jobs are picked up by one or more runbook workers Runs under a service account PowerShell Module SMA PowerShell module to enable management of SMA through cmdlets Service Admin Portal integration Connect the Service Admin portal to the SMA web service

SMA : Architecture and Installation Authoring Debugging Operating Service Management Portal Runbook service PowerShell Modules Runbook Workers REST oData web service Authorizes users Web Service Runbooks Runbook Resources Tracks runbook job state SMA Database Submit requests Runbooks Jobs ModulesActivies Return results SQL Database & ODATA REST Web Service Persist State Pick up Jobs Runbook Workers Http Response Http Request Service Management Portal

Service Management Automation – Minimum Setup

Service Management Automation Check Points Demo

SMA Architecture with Service Manager PowerShell Windows Workflow Foundation Service Management Automation Runtime Service Management Automation Web Service API Windows Azure Pack Admin Portal SMA PowerShell Module/Cmdlets SCSM WorkflowsSCSM Console SMA Cireson SMA Connector

SMA : Runbook Authoring and Tools  Things to consider when creating SMA Runbooks  Check Out:  Tags  Logging  Progress  “Atomic” Runbooks that are modular in nature

Service Management Automation Logging / Progress Demo

SMA : Runbook Authoring and Tools  Easy Import / Export  Use SMART for Runbook Import and Export  service-management-automation-sma-runbook-toolkit-spotlight-smart-for- runbook-import-and-export.aspx service-management-automation-sma-runbook-toolkit-spotlight-smart-for- runbook-import-and-export.aspx

Service Management Automation Import Export Demo

SMA : Working with modules Creating SMA friendly PowerShell modules Include for every cmdlets Synopsis Description Help uri Cmdlet should be able to take in a connection object as a parameter. Cmdlets in the module should be stateless Define output type for all cmdlets (IntelliSense)

SMA Advantages Over “Classic” Orchestrator  64-bit support  Native PowerShell execution and PowerShell 3+ support  Checkpoint/Resume inside runbooks  Runbook servers architecture is more scalable  Save/Test drafts  Versioned runbooks  Schedule runbooks  Parallel processing inside runbooks Text authoring vs. Visual Designer

Integration of Orchestrator and SMA  Orchestrator supports  PowerShell Workflow  Graphical Authoring  Call SMA from Orchestrator  Call Orchestrator from SMA

Moving Runbooks and Concepts from Orchestrator to SMA  Sample migration case & Tools available to help  2-part blog post series about calling an Orchestrator Runbook from SMA, and integrating with Service Manager  1.aspx 1.aspx  Orchestrator and SMA integration in action  integration-points.aspx integration-points.aspx  Smart for Runbook Conversion  sma-runbook-toolkit-spotlight-smart-runbook-conversion-helper.asp sma-runbook-toolkit-spotlight-smart-runbook-conversion-helper.asp

Thank You  Jakob Gottlieb Svendsen   PowerShell User Group 