Service Manager and Orchestrator – The Perfect PartnershipJustin CookData#3 – Principal Consultant (Systems Management)

Jeffrey CookData#3 – Solution Consultant (Systems Management)

MDC324B

Agenda• Service Manager / Orchestrator

• Introduction• Challenges• Orchestrator Tips and Best Practices

• Scenario 1 – Importing Additional CI Data Into CMDB

• Scenario 2 – Notification for a P1 Incident• Scenario 3 – Complex Software Installation

Request• Scenario 4 – Archive Attached Files From Service

Manager• Session Review • Questions (#MDC324B)

Third party management

tools

Service Catalog Templates

Workflows

CMDB

Work

It

em

s

Config

ura

tion

Ite

ms

Know

led

ge

Reporting and data warehousing

Self Service / Reporting

Process Automation

Integration

EmailMobile Portal

ITIL ProcessesChang

eReleaseRequest

Fulfilment

Incident Problem

System Center Service Manager:

Platform for Orchestrating People, Process and Technology

Automation Capabilities Challenges

Self Service Portal

Native Workflows

Email Notifications

System Connectors

Workflows Have Limited Flexibility

High Processor Utilisation

System Connectors Have Fixed Data Imports

System Center Service Manager:

Automation Capabilities and Challenges

System Center Orchestrator: Process Automation That Simplifies Datacenter Management

Integration • Optimise

Heterogeneous Environments

• Easy-to-extend platform

Orchestration• Flexible Process

Workflows• Reliability Across

Multiple Tools and Systems

Automation• Enable IT resources

to Focus on Innovation

• Reduce Error-Prone Manual Activities

Optimise and Extend Existing Investments

Deliver Flexible and Reliable Services

Lower Costs and Improve

Predictability

Integration Packs / Activity Categories

Key Capabilities

Integration Packs Including System Center, Exchange,

AD

System FunctionsScheduling and Monitoring

File ManagementEmail Notification

Event Logging

PowerShell / .NET Scripting

Run Programs

SQL DB Connectivity

File System and Windows

System Center Orchestrator: Integration Packs and Key Capabilities

System Center Orchestrator:Tips and Best Practices

• Number your Folders / Runbooks• PowerShell Options:

• Run .NET Script (32bit PowerShell 2.0)• Invoke-Command cmdlet• PowerShell Variables• PowerShell Integration Pack• Run Program

• Adjust the Runbook Job Concurrency• Include Logging and Rollback• Colour Links in Runbooks

Sample: Catch Errors with Invoke-Command# Setup the script to stop on error$ErrorActionPreference = "Stop"

# Set the name of the server to remote to$RemoteServer = "RemoteServerName"

# Run the script and check for errorstry { # Setup the server to connect to for the remote execution $session = New-PSSession -ComputerName "$RemoteServer"

# Setup the session and connect Invoke-Command -Session $Session -ScriptBlock {

# *** Start Sample Script Content, this is an example only *** # Import the SMLets module Import-Module SMLets # *** End Sample Script Content, this is an example only *** } }

# Catch any errorscatch

{ # Return the error details Throw $_.Exception }

Scenario 1 – Importing Additional CI Data Using Orchestrator

Scenario 1 – Setting the SceneImporting Additional CI Data Using Orchestrator

• Challenges:• Want to import additional data into CMDB• Service Manager connectors are fixed• CSV Connector is manual

• Solution:• Extend user class and form• Utilise a single Orchestrator Runbook for inserting data into CMDB

Demo – Importing Additional CI Data Using OrchestratorJustin Cook

Scenario 2 - Notification for a P1 Incident

Scenario 2 - Setting the SceneNotification for a P1 Incident

• Challenges:• No native SMS integration for Service Manager• No method of identifying on call staff• Requires multiple workflows and subscriptions

• Solution:• Create a custom Configuration Item to identify on call staff• Utilise Orchestrator to locate on call staff and send notifications

Demo – Notification for a P1 Incident

Jeffrey Cook

Scenario 3 - Complex Software Installation Request

Scenario 3 - Setting the SceneComplex Software Installation Request

• Challenges:• ConfigMgr Application Catalog Limitations• How Do We Deploy The Apps• Applications May Require Approval• Review Activities Have Fixed Members

• Solution:• Create a custom class for software packages• Orchestrator delivers flexibility

Demo – Complex Software Installation RequestJustin Cook

Scenario 4 - Archiving Attached Files from Service Manager

Scenario 4 – Setting the SceneArchiving Attached Files from Service Manager

• Challenges:• Attachments are not synced to the Data Warehouse and are removed when database

grooming occurs• Grooming is required to maintain service manager performance• Attachments may be required to be available for a period of time: i.e. Scanned

approvals• Attachments are stored in the Database and not as files

• Solution:• Create some custom properties for tracking the archiving process • Utilse Orchestrator to archive any documents attached in Service Manager, and

populate the Service Manager Objects with information about the archiving

Demo – Archiving Attached Files from Service ManagerJeffrey Cook

Service Manager and Orchestrator

Imagination Is The Only Boundary• Delivers Flexibility• Include Runbooks in SRs for Automation• Populate Review Activities By Group or Title• Skip Review Activities• Add CIs to CMDB from Other Data Sources• Send Notifications based on Complex Workflows• Archive Work Item Attached Files

How To Contact Us• Justin Cook

• Email: Justin_cook@data3.com.au or b-jucook@Microsoft.com• Twitter: @JustinCook78• Blog: systemcentertech.com

• Jeffrey Cook• Email: Jeffrey_cook@data3.com.au or b-jcook@microsoft.com• Twitter: @CookJeffJ

Developer Network

Resources for Developers

http://msdn.microsoft.com/en-au/

Learning

Virtual Academy

http://www.microsoftvirtualacademy.com/

TechNet

Resources

Sessions on Demand

http://channel9.msdn.com/Events/TechEd/Australia/2013

Resources for IT Professionals

http://technet.microsoft.com/en-au/

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