In-Depth Introduction to Service Management AutomationAnders Bengtsson, Principal PFEJohn McCabe, Senior PFE

CDP-B336

During this session we will give you a deep introduction to Service Management Automation (SMA), what it is and when to use it

Agenda

What is SMAHow to use SMAWhen to use SMA

?

SMA = Service Management Automation

How many of you are using SMA today?

What is SMA?

What is SMA… technical definitionWhat is SMA (Service Management Automation) ?

An automation engine based on PowerShell workflows

Difference between Orchestrator and SMA?SMA has its own infrastructureSMA has no drag and drop GUI (today), but can

integrated with Windows Azure Pack (WAP)

Where can I find SMA? On the Orchestrator 2012 R2 installation media

Introduced with PowerShell 3.0Common PowerShell syntaxUtilizes Windows Workflow Foundation (WF)Benefits to PS Workflow

Checkpoint / Suspend Parallel execution across one or more systemsWell suited for long running tasks

*not all PowerShell functionality exists in PS Workflow

What is PowerShell Workflow

Collection of on premise Azure technologiesMulti Tenant, Self Service, cloud experienceAdmin Portal / Tennant Portal

What is the Windows Azure Pack

WAP provides an GUI to SMANative connector between WAP actions and SMA automationWAP is not necessarily necessary for SMA to functionNo Administration Capability from the WAP Tenant Portal

SMA and the Windows Azure Pack

demoIntroduction to SMAAnders BengtssonPrincipal PFEMicrosoft

SMA Architecture

SMA web service

SMA worker

SMA worker

SMA database

Windows Azure PackWAP

Orchestratorweb service

Orchestratordatabase

Orchestratorrunbook servers

Orchestratormanagement

serverPS and WebReq

1. Deploy SMA Components2. Deploy multiple runbook workers3. Enable Log Purge4. Deploy WAP5. Configure WAP Integration

Installation / Post Deployment

Assets: globally available combination of settings

Connections –connection information for external systemsVariable – available to all RunbooksCredentials – PSCredential or CertificateSchedules – Runbook execution schedule

Assets

demoGlobal settings in SMAAnders BengtssonPrincipal PFEMicrosoft

Checkpoint: Snapshot of current stateCheckpoint-Workflow-PSPersist $True placed after activity$PSPersistPreference = $TrueSuspend-Workflow

Suspend: Pause Runbook jobSuspend-Workflow: Checkpoint and Suspend Suspend-SmaJob: Suspend at next checkpointWAP UI: Suspend at next checkpointWorkflow exception / Runbook worker crash

Checkpoint / Suspend

Execute true PowerShell within workflowCreates PowerShell session returning output to workflowCheck Point / Suspend not validWorkflow variables are not visible to inline Script

$Using scope modifier (Example $Using:ComputerName)

Inline Script

Invoke Inline: starting a Runbook by nameParent and all nested compiled into one jobOutput of all Runbooks will be ‘rolled up’Synchronous execution

Start-SmaRunbook: starting using PS cmdletStarts a second jobOutput is specific to each jobAsynchronous execution

Nesting Runbooks

InlineScript: $data = inlinescript { script-content}Inline runbook: $data = invoked-runbookStarted runbook: returns Job ID which can be used with Get-SMAJob

Data Return

demoCheckpointing and Data ReturnAnders BengtssonPrincipal PFEMicrosoft

When to use SMA

When could you use SMA today? No Orchestrator IP exists for the workflow you need to build If you need large number of runbook instances, SMA scales better If you are using WAP already (or looking for an excuse) Any new scenarios where SCO offers no discernable advantage over SMA When using Parallel execution, for example multiple devices When using Check Pointing, for high availability, restartable, interruptible If you have PowerShell skills and no Orchestrator skills it’s easier to start with SMA

than Orchestrator If you don’t know PowerShell and you don’t know Orchestrator then you can use SMA

anyway

SMA and Orchestrator can coexist and integrateBoth can function independentlyOverlap in capabilitiesEach offers a unique set of benefitNo current runbook migration capability

SMA and Orchestrator

DemoOrchestrator and SMA integrationAnders BengtssonPrincipal PFEMicrosoft

What about Service Manager integration?

DemoService Manager and SMA integrationAnders BengtssonPrincipal PFEMicrosoft

Azure Automation

Process automation engine built on PowerShell WorkflowAutomate error-prone, long running, frequently repeated manual tasks to keep your Azure services up and running

Just announced general availability!Want to learn more?CDP-B344 - Introduction to the New Microsoft Azure Automation Service (Oct 30th, 12 PM)

Fault tolerantHighly reliableExtensibleCloud scaleSecure

Come visit us in the Microsoft Solutions Experience (MSE)!Look for the Cloud and Datacenter Platform area TechExpo Hall 7

For more informationWindows Server Technical Previewhttp://technet.microsoft.com/library/dn765472.aspx

Windows Server

Microsoft Azure

Microsoft Azurehttp://azure.microsoft.com/en-us/

System Center

System Center Technical Previewhttp://technet.microsoft.com/en-us/library/hh546785.aspx

Azure Pack Azure Packhttp://www.microsoft.com/en-us/server-cloud/products/windows-azure-pack

AzureImplementing Microsoft Azure Infrastructure Solutions

Classroomtraining

Exams

+

(Coming soon)Microsoft Azure Fundamentals

Developing Microsoft Azure Solutions

MOC

10979

Implementing Microsoft Azure Infrastructure Solutions

Onlinetraining

(Coming soon)Architecting Microsoft Azure Solutions

(Coming soon)Architecting Microsoft Azure Solutions

Developing Microsoft Azure Solutions

(Coming soon)Microsoft Azure Fundamentals

http://bit.ly/Azure-Cert

http://bit.ly/Azure-MVA

http://bit.ly/Azure-Train

Get certified for 1/2 the price at TechEd Europe 2014!http://bit.ly/TechEd-CertDeal

2 5 5MOC

20532

MOC

20533

EXAM

532EXAM

533EXAM

534

MVA MVA

Please Complete An Evaluation FormYour input is important!TechEd Schedule Builder CommNet station or PC

TechEd Mobile appPhone or Tablet

QR code

Evaluate this session

CDP-B353 Automated Workload Provisioning with the Azure Pack and Windows PowerShell CDP-B412 Datacenter Integration Using Automation in System Center 2012 R2 Orchestrator CDP-B245 Automation Roadmap in the Next Release of System Center, Azure Pack, and Microsoft Azure CDP-H310 System Center 2012 R2 Lab 3: Automation and Self-Service

Related content

Use SMA today together with OrchestratorUse SMA today together with Service ManagerNo need for a Private Cloud to run SMASMA solve many Orchestrator challenges

Session Summary

www.contoso.se

Thanks!

© 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.