Stay Classy, With System Center Ramblings from San Diego

How to create an Incident Dashboard using Excel in System Center 2012 SP1 - Service Manager (SCSM) 2012

2013-05-17T23:32:27Z

This blog walks through the steps needed to create a dashboard in Excel that looks like this:

HIGH-LEVEL STEPS:

1) From the Service Manager Console in the data Warehouse pane and the Cubes node, click on a cube and select ‘Analyze Cube in Excel’

2) Create multiple sheets in the excel workbook – each one with a PivotTable and chart

3) Create a new sheet in the excel workbook and copy and paste each of your charts from the sheets you created them on to the new ‘dashboard’ sheet

4) Publish by either storing it in a Service Manager ‘Analysis Library’ so it can be accessed via others by the console, or publish to SharePoint.

NOTE: You may need to add users (preferably via an AD group membership) to the SCDW_Report_Readers Role in SQL Analysis Services, and grant the role access to the cubes and data sources as described here so users have permissions to open up the report and refresh it:

DETAILED STEPS:

1) In the Service Manager console, navigate to Data Warehouse>Cubes and click Service Manager Work Items Cube, then click on ‘Analyze Cube in Excel’

2A) In the first excel sheet, create the ‘Active Incidents by Classification’ Report:

a) Under the PivotTable Fields pane on the right-hand side, Change the Show Fields dropdown on the right-hand side to IncidentDim:

b) Check ‘Incidents Active’

c) Scroll down to IncidentDim_IncidentClassification, expand ‘More Fields and check ‘IncidentClassificationValue’:

d) Click on the Data ribbon and then click the properties button. Ensure ‘Refresh data when opening the file’ is selected.

e) Click on the Pivot Table and then in the Ribbon click PivotTable Tools>ANALYZE and the PivotChart button

f) Choose a bar type chart.

How the areas in the bottom right should be populated:
Filters – Blank
Legend – Blank
Rows - IncidentClassificationValue
Values – Incidents Active

so it looks like this:

2B) In a new Excel Sheet, Create the ‘All Incidents by Status’ report

d) This will open up a new pivot table so you can create a second table selection and chart.
e) Under the PivotTable Fields pane on the right-hand side, Change the Show Fields dropdown on the right-hand side to IncidentDim
f) Check ‘IncidentDimCount’ (This is the total number of incidents in the Warehouse)
g) Scroll down to IncidentDim_IncidentStatus, expand ‘More Fields and check ‘IncidentStatusValue’
h) Click on the Data ribbon and then click the properties button. Ensure ‘Refresh data when opening the file’ is selected.
i) Click on the Pivot table and then in the Ribbon click PivotChartTools>analyze and the PivotChart button
j) Choose a Pie Chart.

How the areas in the bottom right should be populated:
Filters – Blank
Legend – Blank
Axis - IncidentStatusValue
Values – IncidentDimCount

2C) In a new Excel Sheet, Create the ‘Incident SLA Status’ report

a) Create a new worksheet and then click Insert, then choose PivotTable on the far left of the ribbon
b) Check the ‘Use an external data source’ radio button and then click ‘choose connection’
c) Choose the Connection that has an icon with a cube on it and click open.
d) This will open up a new pivot table so you can create a second table selection and chart.
e) Under the PivotTable Fields pane on the right-hand side, Change the Show Fields dropdown on the right-hand side to Incident SLA Instance Information
f) Check ‘IncidentSLAInstanceInformation’ at the top
g) Scroll down to SLAInstanceStatus, expand ‘More Fields and check ‘SLAInstanceStatusValue’
h) Click on the Data ribbon and then click the properties button. Ensure ‘Refresh data when opening the file’ is selected.
i) Click on the Pivot table and then in the Ribbon click PivotChartTools>analyze and the PivotChart button
j) Choose a Pie chart .

How the areas in the bottom right should be populated:
Filters – Blank
Legend– Blank
Rows- SLAInstanceStatusValue
Values – IncidentSLAInstanceInformation

2D) In a new Excel Sheet, Create the ‘All Incidents by Source’ report

a) Create a new worksheet and then click Insert, then choose PivotTable on the far left of the ribbon
b) Check the ‘Use an external data source’ radio button and then click ‘choose connection’
c) Choose the Connection that has an icon with a cube on it and click open.
d) This will open up a new pivot table so you can create a second table selection and chart
e) Under the PivotTable Fields pane on the right-hand side, Change the Show Fields dropdown on the right-hand side to IncidentDim
f) Check ‘IncidentDimCount’ (This is the total number of incidents in the Warehouse)
g) Scroll down to IncidentDim_IncidentSource, expand ‘More Fields and check ‘IncidentSourceValue’
h) Click on the Data ribbon and then click the properties button. Ensure ‘Refresh data when opening the file’ is selected.
i) Click on the Pivot table and then in the Ribbon click PivotChartTools>analyze and the PivotChart button
j) Choose a Pie chart.

How the areas in the bottom right should be populated:
Filters – Blank
Rows– Blank
Axis - IncidentSourceValue
Values – IncidentDimCount

2E) In a new Excel Sheet, Create the ‘Active Incidents by Support group’ report

a) Create a new worksheet and then click Insert, then choose PivotTable on the far left of the ribbon
b) Check the ‘Use an external data source’ radio button and then click ‘choose connection’
c) Choose the Connection that has an icon with a cube on it and click open.
d) This will open up a new pivot table so you can create a second table selection and chart
e) Under the PivotTable Fields pane on the right-hand side, Change the Show Fields dropdown on the right-hand side to IncidentDim
f) Check ‘Incidents Active ’ (This is the total number of Active incidents in the Warehouse)
g) Scroll down to IncidentDim_IncidentTierQueues, expand ‘More Fields and check ‘IncidentTierQueuesValue’
h) Click on the Data ribbon and then click the properties button. Ensure ‘Refresh data when opening the file’ is selected.
i) Click on the Pivot table and then in the Ribbon click PivotChartTools>analyze and the PivotChart button
j) Choose a Pie chart.

How the areas in the bottom right should be populated:
Filters – Blank
Legend – Blank
Rows - IncidentTierQueuesValue
Values – Incidents Active

2F) In a new Excel Sheet, Create the ‘Incidents by resolved Date’ report

a) Create a new worksheet and then click Insert, then choose PivotTable on the far left of the ribbon
b) Check the ‘Use an external data source’ radio button and then click ‘choose connection’
c) Choose the Connection that has an icon with a cube on it and click open.
d) This will open up a new pivot table so you can create a second table selection and chart
e) Under the PivotTable Fields pane on the right-hand side, Change the Show Fields dropdown on the right-hand side to IncidentDim
f) Check ‘IncidentDimCount’ (This is the total number of incidents in the Warehouse)
g) Scroll down to IncidentDim, expand ‘More Fields and check ‘Resolved date’
h) Click on the Data ribbon and then click the properties button. Ensure ‘Refresh data when opening the file’ is selected.
i) Click on the Pivot table and then in the Ribbon click PivotChartTools>analyze and the PivotChart button
j) Choose a Line

how the areas in the bottom right should be populated:
Filters – blank
Legend – blank
Rows - Resolved Date
Values – IncidentDimCount

2G) In a new Excel Sheet, Create the ‘Incidents By Created Date’ report

a) Create a new worksheet and then click Insert, then choose PivotTable on the far left of the ribbon
b) Check the ‘Use an external data source’ radio button and then click ‘choose connection’
c) Choose the Connection that has an icon with a cube on it and click open.
d) This will open up a new pivot table so you can create a second table selection and chart
e) Under the PivotTable Fields pane on the right-hand side, Change the Show Fields dropdown on the right-hand side to IncidentDim
f) Check ‘IncidentDimCount’ (This is the total number of incidents in the Warehouse)
g) Scroll down to IncidentDim, expand ‘More Fields and check ‘Created date’
h) Click on the Data ribbon and then click the properties button. Ensure ‘Refresh data when opening the file’ is selected.
i) Click on the Pivot table and then in the Ribbon click PivotChartTools>analyze and the PivotChart button
j) Choose a Line

How the areas in the bottom right should be populated:
Filters – blank
Legend – blank
Rows - Created Date
Values – IncidentDimCount

3) On a new Excel Sheet, Create the dashboard

a) Create a new worksheet and rename it at the bottom left to ‘dashboard’
b) Copy and paste your charts form the other sheets to this worksheet.
c) Click the ‘View’ ribbon and uncheck formula bar, gridlines, and headings.

d) Click the ‘insert’ ribbon and choose textbox, and type a title such as Incident Dashboard at the top.

4) Publish by either storing it in a Service Manager ‘Analysis Library’ so it can be accessed via others by the console, or publish to SharePoint.

To use the Analysis Library, Create a share where you want to store reports and then specify this share in the Service Manager console underneath data Warehouse>Analysis Library:

Ensure that the Users who will be opening up reports on this share have access to it .

REPEATED NOTE: You may need to add users (preferably via an AD group membership) to the SCDW_Report_Readers and grant the role access to the cubes and data sources as described here so they have permissions to open up the report and refresh it:

ADDITIONAL REFERENCES:

This is a great blog post that talks about publishing to SharePoint using Excel web services: http://blog.scsmfaq.ch/2012/02/06/data-cubes-in-service-manager-2012-part-23-publishing-reports/

MMS 2013 - Advanced Real World System Center Data Warehouse and Reporting: http://channel9.msdn.com/Events/MMS/2013/SD-B316

Service Manager 2012: System Center Data Warehouse, Reporting, and Dashboards http://channel9.msdn.com/Events/MMS/2012/SD-B312

This wiki page contains lots of good links too: http://social.technet.microsoft.com/wiki/contents/articles/15608.system-center-service-manager-data-warehouse-and-reporting.aspx

Creating Reports Using Performance Point: http://blog.concurrency.com/infrastructure/creating-scsm-2012-reports-using-performancepoint/

Operations Manager 2012 Dashboard Widgets

2013-05-13T21:25:23Z

I wrote this as a reference for the Out of the box (OOB) Widgets in Operations Manager 2012 SP1. This is intended to help in putting together custom dashboards using the OOB functionality. A great example of putting this all together can be downloaded here http://blogs.technet.com/b/momteam/archive/2012/06/12/free-windows-server-2008-dashboards-for-opsmgr-2012-and-tool-to-help-create-your-own-customized-dashboards.aspx (Download and import the Xml management packs – Windows.Server.Summary.Dashboard.xml and Windows.Server.Task.Pane.Dashboard.MP.xml):

Also a great recording from MMS 2013 on customizing your dashboards more above and beyond what is OOB can be found here: http://channel9.msdn.com/Events/MMS/2013/IM-B401

My good buddy Mr.Holman has a nice blog on publishing your all-signing, all-dancing dashboards to SharePoint too: http://blogs.technet.com/b/kevinholman/archive/2013/04/03/publishing-scom-2012-dashboards-to-sharepoint.aspx

Two of the widgets are based upon SLAs, so there is a section that talks briefly about SLA Configuration at the end of this post.

DASHBOARD LAYOUTS:

There are 4 types of dashboard that can be created through the UI:

Column Layout
Grid Layout
Service Level Dashboard
Summary Dashboard

Here are some examples each of these layouts:

Column Layout:

The Column layout enables up to 5 vertical columns to displayed in a row in the dashboard.

Example 2-column:

Example 4-Column:

Grid Layout:

The Grid layout allows layouts of 1,2,3,4,5,6 or 9 cells in the following configurations:

Example: 5-cell Dashboard:

Service Level Dashboard:

The Service Level dashboard takes a pre-configured SLO and shows the data for it. The bottom pane updates as you click on a specific instance in the top-left widget:

Summary Dashboard:

A summary dashboard adds an 'Object by Performance’, ‘Performance’ and ‘State’ widget in a 3-cell configuration:

Once created, you set the scope for each widget, depending on what you want to display:

So once you’ve decided on your dashboard layout from the 4 options shown above, your next consideration is what widgets you’d like to include on the dashboard, and what you would like each widget to display.

WIDGETS

Objects by Performance Widget:

This is also known as the ‘Top 10’ dashboard, but it can actually do from a top 1 to top 20, and can also do bottom results. ‘Top results’ can be useful in scenarios such as highest CPU usage. ‘Bottom Results’ can be useful in scenarios such as % Free Disk Space.

Note the (all) instance cannot be used in this view. Therefore you can choose an instance like ‘C:’ and then all the ‘C’ drives will be shown.

Configuration:

Example:

Note, if you don’t see the path, be sure to have System Center 2012 SP1 UR2 deployed. Rather than just looking at the KB for the download and installation instructions, it is always fun to see what ‘feline’ representation our good friend Mr.Holman has allocated to a given CU / update rollup (and he has some pretty nice guidance on deploying it too!)

Object SLA Widget

With this one, pick an appropriate Object (instance of a class) or a group that has an SLA applied to it.

Configuration:

Example:

Performance Widget

This widget creates a performance graph for the selected group / object. In this widget, it is possible to use the (ALL) instance.

Configuration:

Example:

State Widget:

This widget can be based on one of three configurations:

All instances of a specific class (you can skip the group selection)
a specific group and all of it’s member instances, regardless of class type
a Specific group narrowed down to a specific class type contained in the group

Configuration:

Example – SQL DB Engine State:

SLA Widget:

This widget just requires selection of one of your pre-configured SLAs, and will use the group / class that the SLA is scoped on.

Configuration:

Example:

SLA Configuration:

The above is based on the following example SLA configuration (Authoring>Management Pack Objects>Service Level tracking):

Alert Widget:

Allows the display of alerts, narrowed down to a specific group of object, and it is also possible to narrow down on Severity, priority, and Alert Resolution State.

Configuration:

Example:

The alert widget on the far right has the ‘Enable Alert Details inline’ checkbox checked.

Details Widget:

This widget is context-sensitive based on what is selected in a state or alert widget in the same dashboard view.

Configuration:

Example – Alert Details:

Shows the Detail of the Selected Alert:

Example – State Details:

Shows the Detail of the object selected in a state view:

Instance Details Widget:

Unlike the ‘Details’ Widget, this is not context-sensitive and will show the details of a selected group or instance, as selected during configuration of the widget.

Example – SQL DB Engine on ComputerX:

SLA Configuration Note

More detail on configuring SLOs can be found here: http://technet.microsoft.com/en-us/library/hh212753.aspx

Below is a very brief ‘quick-start’ style summary though! They are configured in the Authoring pane under Management Pack Objects> Service Level Tracking.

Two types:

Monitor
Performance Collection Rule

For a Monitor, it is important to know the class that the Monitor is targeted too (which you can find by looking at the monitor properties).

For a performance collection rule, it is important to know the class that the Performance collection rule is targeted to (which you can find by looking at the rule’s properties).

Example of a performance one:

(The example of a monitor-based Service Level Objective can be found above in the SLA Widget section)

You can test your SLA data by running the “Service Level Tracking Summary report’ which can be found in the Microsoft Service Level Report library Folder in the reporting pane.

Here is the example output report:

Happy Dashboarding!!!!

Microsoft Management Summit (MMS) 2013 Video Recording Catalog

2013-05-03T19:31:14Z

All these recordings can be accessed on the MSDN / Channel 9 website. This post organizes the sessions by product / technology to try and make it easier to find what you’re looking for! Where a combination or the integration between products is a focus, I have duplicated the links in the appropriate sections.

Also, if you want to get really fancy check out my colleague Stefan’s cool solution for downloading with PowerShell

http://blogs.technet.com/b/stefan_stranger/archive/2013/04/14/download-mms-2013-videos-from-channel-9.aspx

Enjoy!

SYSTEM CENTER OPERATIONS MANAGER (MMS 2013)

Monitoring Applications Using APM, Global Service Monitor, and Visual Studio Web Testing

Managing Linux and UNIX in a System Center Private Cloud

System Center 2012 SP1 Operations Manager Overview

DevOps and Operations Manager: New Management Packs

Developers and Operations Engineers: System Center and Visual Studio

DevOps: Global Service Monitoring with System Center Operations Manager 2012 SP1

DevOps: Azure Monitoring & Authoring Updates for Operations Manager 2012 SP1

Workloads- Managing Windows, IIS & SQL Technologies

Monitoring and Managing the Network and Storage Infrastructure with Operations Manager 2012

Panel Discussion- System Center Operations Manager

Monitoring Beyond SQL Server- Oracle DB, DB2, Informix, and MySQL

Hacking the Data Warehouse- Mastering the Reporting Experience in System Center 2012 Operations…

Utilizing and Developing Dashboards in Operations Manager 2012 SP1

Debug Production Application Issues using System Center Operations Manager

Effective Capacity Planning of Your Infrastructure Resources

Mission- IT Operations for a Good Night's Sleep

SQL Server 2012 for System Center Administrators

Manage and Monitor Your Windows Azure Usage From System Center 2012 SP1

Interview- DevOps- Global Service Monitoring with System Center Operations Manager 2012 SP1

Interview- Managing Linux and UNIX in a System Center 2012 Private Cloud

SYSTEM CENTER CONFIGURATION MANAGER 2012 (MMS 2013)

Managing Embedded Devices with Configuration Manager 2012

Hierarchy Simplification with Configuration Manager 2012

Customer Panel Discussion: Successes and Lessons Learned in Unified Device Management

Manage ALL of Your Devices Just Like You Manage Your Windows PCs with System Center

Application Delivery with System Center 2012 Configuration Manager SP1 and Windows Intune

Reduce IT Energy Waste and Implement PC Power Management

Augmenting Your Windows Management Strategy with System Center 2012 Configuration Manager Task…

Boundaries in System Center Configuration Manager 2012

How Microsoft IT Uses System Center Configuration Manager 2012 SP1

Notes From the Field- Complex and Massive Configuration Manager Migrations

Compliance Settings and Control End–User Installed Software

Advanced Infrastructure for System Center 2012 Configuration Manager SP1

Deploying and Managing Windows 8 with Configuration Manager 2012 SP1

Deploying System Center 2012 Configuration Manager SP1 With Windows Intune

Documentation, Disaster Recovery, and Using Scripts as Time Savers

Replacing BIOS With a UEFI Deployment

Migrating From Configuration Manager 2007 to Configuration Manager 2012

Manageability of Mac & Linux Using System Center 2012 Configuration Manager SP1

How Microsoft IT Upgrades System Center Configuration Manager 2012 Hierarchy with System Center…

Configuration Manager 2012- MVP Experts Panel

Software Deployments- From GPO–Based to Configuration Manager

SQL Server 2012 for System Center Administrators

System Center 2012 Configuration Manager SP1 Overview

Managing Third Party Updates with System Center 2012 Configuration Manager SP1

The WHY of Configuration Manager- Methods of Deployment

The Top Ten Lessons Learned in Managing SQL & Reporting

Top Shops- Field Notes from IT Departments That Rock

System Center 2012 Configuration Manager SP1 and Windows Intune: Unified Modern Device Management

System Center 2012 Endpoint Protection Integration With Configuration Manager 2012 SP1

What’s New with Microsoft Deployment Toolkit 2012 Update 1

What's New- Configuration Manager 2012 SP1 Infrastructure Improvements and Hierarchy Design

Windows Intune Overview

Reporting in System Center 2012 Configuration Manager SP1

System Center 2012 Configuration Manager SP1 Case Studies and Migration Experiences

Complex Maintenance Using System Center 2012 Configuration Manager and Orchestrator- Patching a…

Configuration Manager 2012 and Orchestrator 2012

Deploy All of System Center- Two Real World Examples

Large Scale System Center Configuration Manager Environments- Challenges and Solutions

The MMS 2013 Treasure Hunt- Hidden Gems & Diamonds in Configuration Manager 2012

System Center Configuration Manager 2012 Jeopardy Quiz

Configuration Manager 2012- Data Collection

Infrastructure Changes for System Center 2012 Configuration Manager SP1- Advanced Topics and…

Migration Best Practices from System Center Configuration Manager 2007 to 2012

Configuration Manager 2012- Software Updates

Truly Better Together- Configuration Manager 2012 SP1 and PowerShell

Advanced SQL Query Techniques- Beyond the Basics

Configuration Manager ... Actually

Streamline Your Configuration Manager 2012 Infrastructure to Make OSD Business as Usual

DEPLOYMENT (MMS 2013)

What’s New with Microsoft Deployment Toolkit 2012 Update 1

Demonstrations of Assessment and Deployment Kit Tools

Advanced Microsoft Deployment Toolkit 2012 Update 1 Customizations

Deploying Windows 8 Using Lite Touch

Choosing the Right OS Deployment Tool

Real World Windows 8 Deployment with MDT 2012 Update 1

Deploying Windows To Go in the Real World

What's New in Windows 8 Deployment

Streamline Your Configuration Manager 2012 Infrastructure to Make OSD Business as Usual

Automating System Center Deployment with the Powershell Deployment Toolkit

The WHY of Configuration Manager- Methods of Deployment

WINDOWS INTUNE (MMS 2013)

Becoming a Windows Intune IT Administrator: A Real-World Perspective

Application Delivery with System Center 2012 Configuration Manager SP1 and Windows Intune

SYSTEM CENTER SERVICE MANAGER (MMS 2013)

Configuring Service Manager for Performance and Scale

Best in Breed Together: Real World Scenarios with Service Manager and Orchestrator

Case Studies of Implementation of Automating Service Request Catalogs with Service Manager

Mission- IT Operations for a Good Night's Sleep

Getting Started with Orchestrator and Service Manager

Advanced Real World System Center Data Warehouse and Reporting

SQL Server 2012 for System Center Administrators

SYSTEM CENTER ORCHESTRATOR (MMS 2013)

Best Practices For Runbook Authoring and Managing Orchestrator

Orchestrator Best Practices: Lessons Learned at Cargill

Getting Started with Orchestrator and Service Manager

What's New with Orchestrator Integration Packs for System Center and SP1

Best in Breed Together: Real World Scenarios with Service Manager and Orchestrator

Configuration Manager 2012 and Orchestrator 2012

Orchestrating Hyper-V Replica Planned Failover with System Center 2012 SP1

Orchestrating Azure and System Center 2012

Provisioning in System Center- Users, Groups, Virtual Servers, Software and More!

SQL Server 2012 for System Center Administrators

Interview- Orchestrating Azure & Hyper-V with System Center 2012

SYSTEM CENTER VIRTUAL MACHINE MANAGER / HYPER-V (MMS 2013)

Getting Started with Virtual Machine Manager and App Controller

Implementing Common Storage Scenarios in Windows Server 2012 with System Center Virtual Machine…

Implementing Common Scenarios in Virtual Machine Manager: Services and Service Templates

Building UI Add–Ins For System Center 2012 SP1 Virtual Machine Manager

Competitive Advantages of the Microsoft Private Cloud over the VMware vCloud

System Center 2012 SP1 Virtual Machine Manager- Managing Large Datacenters

System Center 2012 for VMware Infrastructure

Troubleshooting Common System Center 2012 SP1 Virtual Machine Manager Issues

What's New in System Center 2012 Virtual Machine Manager

SQL Server 2012 for System Center Administrators

Competitive Advantages of Hyper-V over VMware vSphere

Windows Server Virtual Machine- Adding Windows Azure Services

How to Design and Configure Networking in VMM and HyperV (Part 1 of 2)

How to Design and Configure Networking in VMM and HyperV (Part 2 of 2)

Switching to Hyper–V- Migrating from VMware

Cisco Virtual Networking Solutions for Microsoft Hyper-V Environments

Getting Started with Windows Azure Virtual Machines and Virtual Networks

Business Continuity with System Center

Switching to Hyper–V- Migrating from VMware

What's New in Windows Server 2012 Hyper–V

Save Time and Money- Automate Hyper-V with PowerShell and C#

SYSTEM CENTER DATA PROTECTION MANAGER (MMS 2013)

Using Data Protection Manager to Protect your Private Clouds

http://channel9.msdn.com/Events/MMS/2013/IM-B315

SQL Server 2012 for System Center Administrators

CLIENT (MMS 2013)

A Geek's Guide to USMT 5.0

Implementing the Windows To Go Concept in an Enterprise

Application Compatibility for Windows 8

Building the Perfect Windows 8 Image

Deploying and Managing Virtual Applications and Settings with System Center

Deploying Windows 8 Using Lite Touch

Choosing the Right OS Deployment Tool

Develop a Successful Flexible Desktop Strategy in Today’s Digital Era

Windows Sysinternals Primer

What's New with Windows 8 Bitlocker and Microsoft BitLocker Administration and Management 2.0

Maximizing Windows 8 Performance: Troubleshooting Tips

Internet Explorer 10 Administration

Real World Windows 8 Deployment with MDT 2012 Update 1

Deploying Windows To Go in the Real World

What's New in Windows 8 Deployment

Windows RT in the Enterprise

Windows Store Apps: Enterprise LOB App Deployment Scenarios

Making PC Recovery Easier with the Microsoft Diagnostics and Recovery Toolset

Advanced Automation Using Windows Powershell

Windows 8 Security Internals

Managing Embedded Devices with Configuration Manager 2012

DESKTOP VIRTUALIZATION (MMS 2013)

Microsoft Server 2012 Desktop Virtualization (VDI) on Dell Active Infrastructure

Designing a Virtual Desktop Infrastructure Architecture for Scale and Performance

Better Together: Microsoft Application Virtualization 5.0 and Office

Microsoft Application Virtualization 5.0: Migration and Coexistence

How to Manage and Deploy Microsoft User Experience Virtualization Across an Enterprise

Optimizing Windows 8 for Virtual Desktop Infrastructure

What's New in Windows Server 2012 Virtual Desktop Infrastructure and Remote Desktop Services

Deploying and Managing Virtual Applications and Settings with System Center

What’s Next from Citrix- Manage, Migrate and Monitor Desktops and Applications using Microsoft…

Interview- Microsoft Application Virtualization 5.0- Migration and Coexistence

SYSTEM CENTER SUITE / PRIVATE CLOUD (MMS 2013)

Efficient and Agile Infrastructure Management for Cloud Environments

Using Data Protection Manager to Protect your Private Clouds

System Center 2012 SP1 Virtual Machine Manager- Managing Large Datacenters

Competitive Advantages of the Microsoft Private Cloud over the VMware vCloud

Microsoft Private Cloud Fast Track v3- Private Cloud Reference Architecture Based on Server 2012

Inside Windows Server 2012 Deployment and Multi-Server Management Capabilities

Deploying and Managing Linux with Windows Azure

Manage and Monitor Your Windows Azure Usage From System Center 2012 SP1

File Storage Strategies for Private Cloud

Take Control of the Cloud with the Windows Azure PowerShell Cmdlets

Cloud Clustering- Leveraging System Center 2012 for Continual Availability in the Private Cloud

Availability Strategies for a Resilient Private Cloud

SQL Server 2012 for System Center Administrators

Maximize the Benefits of Microsoft Private Cloud- Automation, Self-service and Provisioning

Early Adopters of System Center 2012 SP1

Enabling Hosted IaaS Clouds Using System Center 2012 SP1 with Windows Server

Provisioning in System Center- Users, Groups, Virtual Servers, Software and More!

Cloud Optimize Your Business with Microsoft Management Solutions

The 2012 Release Wave Licensing Recap

Private Cloud Storage Management Best Practices with Microsoft and EMC Solutions

Availability Strategies for a Resilient Private Cloud

Effective Capacity Planning of Your Infrastructure Resources

Fundamentals of Building Clouds

Optimize Your Data Center with Datacenter Services from Microsoft Services

Efficient and Agile Infrastructure Management for Cloud Environments

Customer Panel Discussion- Successes and Lessons Learned in Datacenter Management

Mission- IT Operations for a Good Night's Sleep

Advanced Real World System Center Data Warehouse and Reporting

System Center 2012 SP1 Simplifications and Upgrades

Automating System Center Deployment with the Powershell Deployment Toolkit

How to Build Your Strategy For a Private Cloud

Orchestrating Azure and System Center 2012

Orchestrating Hyper-V Replica Planned Failover with System Center 2012 SP1

Best in Breed Together: Real World Scenarios with Service Manager and Orchestrator

Automate your Infrastructure- Programmatic Management of Cisco UCS with Microsoft System Center

HP Private Cloud Management with System Center

ACCESS & INFORMATION PROTECTION (MMS2013)

The Benefits and Reasons for Upgrading to Windows Server 2012 Active Directory

Using Dynamic Access Control and Rights Management for Information Protection

Using Dynamic Access Control for Compliance and Data Leakage Prevention

Automating Privileged Identity Management with Lieberman Software

Windows 8 Security Internals

Windows Azure and Active Directory

Windows Server 2012- Private Cloud and Security

Securing User Access with Multi-Factor Authentication

WINDOWS SERVER (MMS 2013)

Windows Server 2012 in 60 Minutes

Introduction to Failover Clustering with Windows Server 2012

Deploy All of System Center- Two Real World Examples

Implementing Common Storage Scenarios in Windows Server 2012 with System Center Virtual Machine…

Inside Windows Server 2012 Deployment and Multi-Server Management Capabilities

Software Defined Networking with Windows Server 2012, System Center 2012 SP1 and Partner Solutions

What's New in Windows Server 2012 Hyper–V

Windows Server 2012- Private Cloud and Security

Optimize Your Data Center with Datacenter Services from Microsoft Consulting Services

Save Time and Money- Automate Hyper-V with PowerShell and C#

WINDOWS AZURE (MMS 2013)

Windows Azure and Active Directory

Windows Azure in the Enterprise

Windows Azure Security Overview

Deploying and Managing Linux with Windows Azure

Manage and Monitor Your Windows Azure Usage From System Center 2012 SP1

StorSimple- Enabling Windows Azure Storage for Enterprise

Interview- Windows Azure in the Enterprise

Getting Started with Windows Azure Virtual Machines and Virtual Networks

MMS / COMMUNITY (MMS 2013)

Serverquarium Unwrapped- The HP Cloud Solution for Microsoft that Powers MMS Hands On Labs

MMS 101- Conquering the Summit

Open Sourced- myITforum Unplugged

Up the Creek- Centralize and Maximize System Center Support

Neural Networks for IT Professionals

Keynote Demo Deconstruction

The 2012 Release Wave Licensing Recap

INTERVIEWS (MMS 2013)

Interview- Software Defined Networking with Windows Server 2012, System Center 2012 SP1 and Part

Interview- Manage and Monitor Your Windows Azure Usage From System Center 2012 SP1

Interview- Becoming a Windows Intune IT Administrator- A Real-World Perspective

Interview- Developers and Operations Engineers- System Center 2012 SP1 and Visual Studio 2012

Interview- Windows Server Virtual Machine- Adding Windows Azure Services

Interview- Microsoft Application Virtualization 5.0- Migration and Coexistence

Interview- The Benefits and Reasons for Upgrading to Windows Server 2012 Active Directory

Interview- Windows Server 2012 in 60 minutes

Interview- What's New in Windows Server 2012 Virtual Desktop Infrastructure and Remote Desktop…

Interview- Avanade Partner Interview

Interview- Microsoft Private Cloud Fast Track v3- Private Cloud Reference Architecture Based on…

Interview- Managing Linux and UNIX in a System Center 2012 Private Cloud

Interview- DevOps- Global Service Monitoring with System Center Operations Manager 2012 SP1

Interview- Windows Azure in the Enterprise

Interview- System Center 2012 for VMware Infrastructure

Interview- Using Dynamic Access Control and Rights Management for Information Protection

Interview- Orchestrating Azure & Hyper-V with System Center 2012

Sending out the most recent Analyst Comment from the Action Log in Service Manager 2012

2013-03-22T06:06:13Z

When an analyst adds a comment to the action log, it may be desirable to send this new comment out to the affected user with a nice email update like this:

This blog post walks through how to do it.

Firstly, in order to get a nicer looking email like the one above, start by creating the email in word how you want it to look:

I use these menu options to get my table:

and when done, save this as an HTML doc:

Open the HTML file in notepad or your text editor of choice.

Then create a notification template based on the class ‘Trouble Ticket Analyst Comments’

Copy the HTML from your text editor into the Service Manager template and don’t forget to click the “send as HTML’ checkbox!!!:

You remembered to check ‘Send as HTML’ right? I always forget that one

And then you can add your values. I came across some slightly bizarre behavior here (if I figure out the ins-and-outs of this, I will blog it, or if you know – please feel free to comment ) in that you had to add the value in a different way depending on if it is a service request or incident being updated. Therefore, in order for this to apply to both incidents and service requests, every value you insert has to be inserted twice using a slightly different format.

Let’s start with the subject line:

To add the ID if it’s an incident, click the Insert button, then’ Has Analyst Comment’, then in Available Properties, type ID, scroll down and choose the ID value shown under Work Item and click the Add button:

The only difference for the SR value, is that you click ‘Work Item has comment log’ rather than ‘Has Analyst Comment’, then in Available Properties, type ID, and then scroll down and choose the ID value shown under work item and click the Add button:

NOTE be sure to have a space between 2 strings, as shown below

$Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItem.TroubleTicketHasAnalystComment' SeedRole='Target' TypeConstraint='CustomSystem_WorkItem_Library!System.WorkItem']/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Id$ $Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItemHasCommentLog' SeedRole='Target' TypeConstraint='CustomSystem_WorkItem_Library!System.WorkItem']/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Id$ Updated with Comment

Next you need to find all the placeholders you put in the word doc, and use the ‘Insert’ button to replace these with the strings that will bring in the actual values from the Incident / SR. In my experience, you always seem to find it about two thirds / three quarters of the way down if you created the HTML using word like I did:

Highlight over the placeholder (placeholderID in this case) and then click the Insert button

(Notice how I’m missing ‘Send as HTML’ above – that’s just me checking you’re paying attention )

Now it’s the same as how you added the ID in the subject line (remember to do once using the ‘Has analyst comment’ related class, and once using the ‘Work Item Has comment Log’ related class, to catch it for both Incidents and service requests.

And then repeat this for the other placeholder fields. So for instance with Title, use the ‘Has Analyst Comment’ title first:

Please don’t forget the space! And then do the same for ‘Work Item Has comment log’:

For My ‘Assigned Analyst’ I use the Entered by value under ‘Trouble Ticket Analyst Comments’ (this only needs to be selected once):

For comment you can use this one and it only needs to be selected once also:

I ended up with this as my body:

<head>
< meta http-equiv=Content-Type content="text/html; charset=windows-1252">
< meta name=ProgId content=Word.Document>
< meta name=Generator content="Microsoft Word 14">
< meta name=Originator content="Microsoft Word 14">
< link rel=File-List href="CommnetUpdate_files/filelist.xml">
< !--[if gte mso 9]><xml>
< o:DocumentProperties>
< o:Author>Administrator</o:Author>
< o:LastAuthor>Administrator</o:LastAuthor>
< o:Revision>1</o:Revision>
< o:TotalTime>11</o:TotalTime>
< o:Created>2013-03-22T04:49:00Z</o:Created>
< o:LastSaved>2013-03-22T05:00:00Z</o:LastSaved>
< o:Pages>1</o:Pages>
< o:Words>31</o:Words>
< o:Characters>178</o:Characters>
< o:Company>Microsoft Corporation</o:Company>
< o:Lines>1</o:Lines>
< o:Paragraphs>1</o:Paragraphs>
< o:CharactersWithSpaces>208</o:CharactersWithSpaces>
< o:Version>14.00</o:Version>
< /o:DocumentProperties>
< o:OfficeDocumentSettings>
< o:AllowPNG/>
< /o:OfficeDocumentSettings>
< /xml><![endif]-->
< link rel=themeData href="CommnetUpdate_files/themedata.thmx">
< link rel=colorSchemeMapping href="CommnetUpdate_files/colorschememapping.xml">
< !--[if gte mso 9]><xml>
< w:WordDocument>
< w:SpellingState>Clean</w:SpellingState>
< w:GrammarState>Clean</w:GrammarState>
< w:TrackMoves>false</w:TrackMoves>
< w:TrackFormatting/>
< w:PunctuationKerning/>
< w:ValidateAgainstSchemas/>
< w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
< w:IgnoreMixedContent>false</w:IgnoreMixedContent>
< w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
< w:DoNotPromoteQF/>
< w:LidThemeOther>EN-US</w:LidThemeOther>
< w:LidThemeAsian>X-NONE</w:LidThemeAsian>
< w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
< w:Compatibility>
 < w:BreakWrappedTables/>
 < w:SnapToGridInCell/>
 < w:WrapTextWithPunct/>
 < w:UseAsianBreakRules/>
 < w:DontGrowAutofit/>
 < w:SplitPgBreakAndParaMark/>
 < w:EnableOpenTypeKerning/>
 < w:DontFlipMirrorIndents/>
 < w:OverrideTableStyleHps/>
</w:Compatibility>
< m:mathPr>
 < m:mathFont m:val="Cambria Math"/>
 < m:brkBin m:val="before"/>
 < m:brkBinSub m:val="--"/>
 < m:smallFrac m:val="off"/>
 < m:dispDef/>
 < m:lMargin m:val="0"/>
 < m:rMargin m:val="0"/>
 < m:defJc m:val="centerGroup"/>
 < m:wrapIndent m:val="1440"/>
 < m:intLim m:val="subSup"/>
 < m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
< /xml><![endif]-->
< style>
< !--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-520084737 -1073683329 41 0 479 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-noshow:yes;
mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-unhide:no;
mso-style-locked:yes;
mso-style-link:"Balloon Text";
mso-ansi-font-size:8.0pt;
mso-bidi-font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-ascii-font-family:Tahoma;
mso-hansi-font-family:Tahoma;
mso-bidi-font-family:Tahoma;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
.MsoPapDefault
{mso-style-type:export-only;
margin-bottom:10.0pt;
line-height:115%;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.WordSection1
{page:WordSection1;}
-->
< /style>
< !--[if gte mso 10]>
< style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
table.MsoTableGrid
{mso-style-name:"Table Grid";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-priority:59;
mso-style-unhide:no;
border:solid windowtext 1.0pt;
mso-border-alt:solid windowtext .5pt;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-border-insideh:.5pt solid windowtext;
mso-border-insidev:.5pt solid windowtext;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
table.MsoTableMediumGrid1Accent3
{mso-style-name:"Medium Grid 1 - Accent 3";
mso-tstyle-rowband-size:1;
mso-tstyle-colband-size:1;
mso-style-priority:67;
mso-style-unhide:no;
border:solid #B3CC82 1.0pt;
mso-border-themecolor:accent3;
mso-border-themetint:191;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-border-insideh:1.0pt solid #B3CC82;
mso-border-insideh-themecolor:accent3;
mso-border-insideh-themetint:191;
mso-border-insidev:1.0pt solid #B3CC82;
mso-border-insidev-themecolor:accent3;
mso-border-insidev-themetint:191;
mso-tstyle-shading:#E6EED5;
mso-tstyle-shading-themecolor:accent3;
mso-tstyle-shading-themetint:63;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
table.MsoTableMediumGrid1Accent3FirstRow
{mso-style-name:"Medium Grid 1 - Accent 3";
mso-table-condition:first-row;
mso-style-priority:67;
mso-style-unhide:no;
mso-ansi-font-weight:bold;
mso-bidi-font-weight:bold;}
table.MsoTableMediumGrid1Accent3LastRow
{mso-style-name:"Medium Grid 1 - Accent 3";
mso-table-condition:last-row;
mso-style-priority:67;
mso-style-unhide:no;
mso-tstyle-border-top:2.25pt solid #B3CC82;
mso-tstyle-border-top-themecolor:accent3;
mso-tstyle-border-top-themetint:191;
mso-ansi-font-weight:bold;
mso-bidi-font-weight:bold;}
table.MsoTableMediumGrid1Accent3FirstCol
{mso-style-name:"Medium Grid 1 - Accent 3";
mso-table-condition:first-column;
mso-style-priority:67;
mso-style-unhide:no;
mso-ansi-font-weight:bold;
mso-bidi-font-weight:bold;}
table.MsoTableMediumGrid1Accent3LastCol
{mso-style-name:"Medium Grid 1 - Accent 3";
mso-table-condition:last-column;
mso-style-priority:67;
mso-style-unhide:no;
mso-ansi-font-weight:bold;
mso-bidi-font-weight:bold;}
table.MsoTableMediumGrid1Accent3OddColumn
{mso-style-name:"Medium Grid 1 - Accent 3";
mso-table-condition:odd-column;
mso-style-priority:67;
mso-style-unhide:no;
mso-tstyle-shading:#CDDDAC;
mso-tstyle-shading-themecolor:accent3;
mso-tstyle-shading-themetint:127;}
table.MsoTableMediumGrid1Accent3OddRow
{mso-style-name:"Medium Grid 1 - Accent 3";
mso-table-condition:odd-row;
mso-style-priority:67;
mso-style-unhide:no;
mso-tstyle-shading:#CDDDAC;
mso-tstyle-shading-themecolor:accent3;
mso-tstyle-shading-themetint:127;}
< /style>
< ![endif]-->
< /head>

Your Incident / Service Request was just
updated:<o:p></o:p>

<table class=MsoTableMediumGrid1Accent3 border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none;mso-border-alt:solid windowtext .25pt;
mso-yfti-tbllook:1184;mso-padding-alt:0in 5.4pt 0in 5.4pt;mso-border-insideh:
.25pt solid windowtext;mso-border-insidev:.25pt solid windowtext'>
< tr style='mso-yfti-irow:-1;mso-yfti-firstrow:yes'>
<td width=319 valign=top style='width:239.4pt;border:solid windowtext 1.0pt;
mso-border-alt:solid windowtext .25pt;background:#E6EED5;mso-background-themecolor:
accent3;mso-background-themetint:63;padding:0in 5.4pt 0in 5.4pt'>
ID<o:p></o:p>
</td>
<td width=319 valign=top style='width:239.4pt;border:solid windowtext 1.0pt;
border-left:none;mso-border-left-alt:solid windowtext .25pt;mso-border-alt:
solid windowtext .25pt;background:#E6EED5;mso-background-themecolor:accent3;
mso-background-themetint:63;padding:0in 5.4pt 0in 5.4pt'>
$Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItem.TroubleTicketHasAnalystComment' SeedRole='Target' TypeConstraint='CustomSystem_WorkItem_Library!System.WorkItem']/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Id$ $Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItemHasCommentLog' SeedRole='Target' TypeConstraint='CustomSystem_WorkItem_Library!System.WorkItem']/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Id$<o:p></o:p>
</td>
< /tr>
< tr style='mso-yfti-irow:0'>
<td width=319 valign=top style='width:239.4pt;border:solid windowtext 1.0pt;
border-top:none;mso-border-top-alt:solid windowtext .25pt;mso-border-alt:
solid windowtext .25pt;background:#CDDDAC;mso-background-themecolor:accent3;
mso-background-themetint:127;padding:0in 5.4pt 0in 5.4pt'>
Title<o:p></o:p>
</td>
<td width=319 valign=top style='width:239.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
mso-border-top-alt:solid windowtext .25pt;mso-border-left-alt:solid windowtext .25pt;
mso-border-alt:solid windowtext .25pt;background:#CDDDAC;mso-background-themecolor:
accent3;mso-background-themetint:127;padding:0in 5.4pt 0in 5.4pt'>
$Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItem.TroubleTicketHasAnalystComment' SeedRole='Target' TypeConstraint='CustomSystem_WorkItem_Library!System.WorkItem']/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Title$ $Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItemHasCommentLog' SeedRole='Target' TypeConstraint='CustomSystem_WorkItem_Library!System.WorkItem']/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Title$<o:p></o:p>
</td>
< /tr>
< tr style='mso-yfti-irow:1'>
<td width=319 valign=top style='width:239.4pt;border:solid windowtext 1.0pt;
border-top:none;mso-border-top-alt:solid windowtext .25pt;mso-border-alt:
solid windowtext .25pt;background:#E6EED5;mso-background-themecolor:accent3;
mso-background-themetint:63;padding:0in 5.4pt 0in 5.4pt'>
Status<o:p></o:p>
</td>
<td width=319 valign=top style='width:239.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
mso-border-top-alt:solid windowtext .25pt;mso-border-left-alt:solid windowtext .25pt;
mso-border-alt:solid windowtext .25pt;background:#E6EED5;mso-background-themecolor:
accent3;mso-background-themetint:63;padding:0in 5.4pt 0in 5.4pt'>
$Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItem.TroubleTicketHasAnalystComment' SeedRole='Target' TypeConstraint='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Status$ $Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItemHasCommentLog' SeedRole='Target' TypeConstraint='CustomSystem_WorkItem_ServiceRequest_Library!System.WorkItem.ServiceRequest']/Property[Type='CustomSystem_WorkItem_ServiceRequest_Library!System.WorkItem.ServiceRequest']/Status$<o:p></o:p>
</td>
< /tr>
< tr style='mso-yfti-irow:2'>
<td width=319 valign=top style='width:239.4pt;border:solid windowtext 1.0pt;
border-top:none;mso-border-top-alt:solid windowtext .25pt;mso-border-alt:
solid windowtext .25pt;background:#CDDDAC;mso-background-themecolor:accent3;
mso-background-themetint:127;padding:0in 5.4pt 0in 5.4pt'>
Assigned
Analyst<o:p></o:p>
</td>
<td width=319 valign=top style='width:239.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
mso-border-top-alt:solid windowtext .25pt;mso-border-left-alt:solid windowtext .25pt;
mso-border-alt:solid windowtext .25pt;background:#CDDDAC;mso-background-themecolor:
accent3;mso-background-themetint:127;padding:0in 5.4pt 0in 5.4pt'>
$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem.CommentLog']/EnteredBy$<o:p></o:p>
</td>
< /tr>
< tr style='mso-yfti-irow:3;mso-yfti-lastrow:yes'>
<td width=319 valign=top style='width:239.4pt;border:solid windowtext 1.0pt;
border-top:none;mso-border-top-alt:solid windowtext .25pt;mso-border-alt:
solid windowtext .25pt;background:#E6EED5;mso-background-themecolor:accent3;
mso-background-themetint:63;padding:0in 5.4pt 0in 5.4pt'>
Comment<o:p></o:p>
</td>
<td width=319 valign=top style='width:239.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
mso-border-top-alt:solid windowtext .25pt;mso-border-left-alt:solid windowtext .25pt;
mso-border-alt:solid windowtext .25pt;background:#E6EED5;mso-background-themecolor:
accent3;mso-background-themetint:63;padding:0in 5.4pt 0in 5.4pt'>
$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem.CommentLog']/Comment$<o:p></o:p>
</td>
< /tr>
< /table>

<o:p> </o:p>

From
the IT ServiceDesk<o:p></o:p>

<o:p> </o:p>

</div>

</body>

</html>

and this was my subject:

And all we need to do now is create the subscription.

Be sure to use ‘When an object of the selected class is created’ (we are keying off a new comment being created – remember the class we picked) and select the same targeted Class we based the notification template on (Trouble Ticket Analyst Comments):

You may also like to add the following clause in ‘Additional Criteria’ so that if the Analyst marks it as Private, it does not get sent out to the Affected User (you might want to test this first ):

In the template page, you will select the template we just put all that fine work into:

We will not select anyone in Recipient as instead we are going to take advantage of ‘Related Recipients’:

In Related Recipients, choose the affected user for both ‘Has Analyst Comment’ and ‘Work Item Has Comment Log’ and then we will send it out to the affected user regardless of if it is an incident or a service request:

and your end result should be:

You could also add the Assigned Analyst also if you wanted to, so they get confirmation via email of the update they made:

And that’s it!! Try updating an Incident / SR, and the end result will look something like this:

Happy Notifying!

Setting Status using PowerShell and converting this into a custom task in Service Manager 2012 SP1

2013-03-22T04:27:00Z

I had a customer who had a need this week to manually force the status of service requests / activities into ‘in progress’ or ‘Completed’.

The most common example I see of this is a need to automatically close service requests / incidents after they have been resolved for x amount of time.

Travis also talks about a common example here where it is sometimes required to reactivate a closed incident.

And one more example is if you have custom status values for work items like Incidents and Service Requests, and need to be able to set the work item to one of those.

As far as the auto-close goes, Cireson currently have a free download that is very popular with a lot of folks to that allows configuration of auto-close workflows through the UI:

For the other scenarios described above, it is possible to set status is by launching PowerShell and running the following commands:

(if you upgraded from Service Manager 2010)

cd [installation drive]\program files\Microsoft System Center\Service Manager 2010\Powershell

e.g.

cd C:\program files\Microsoft System Center\Service Manager 2010\Powershell

(if you started on Service Manager 2012)

cd [installation drive]\program files\Microsoft System Center 2012\Service Manager\Powershell

e.g.

cd C:\program files\Microsoft System Center 2012\Service Manager\Powershell

From here the commands are the same regardless of your upgrade / install path:

import-module System.Center.Service.Manager.psd1

To change a manual activity to ‘In Progress’:

(get-scsmclass -name "System.WorkItem.activity.ManualActivity" | get-scsmclassinstance) | where {$_.ID -eq 'MA1416'} | %{ $_.Status = "In Progress" ; $_ } | update-scsmclassinstance

To change a manual activity to ‘Completed’:

(get-scsmclass -name "System.WorkItem.activity.ManualActivity" | get-scsmclassinstance) | where {$_.ID -eq 'MA1416'} | %{ $_.Status = "Completed" ; $_ } | update-scsmclassinstance

To change a Service Request to ‘In Progress’:

(get-scsmclass -name "System.WorkItem.ServiceRequest" | get-scsmclassinstance) | where {$_.ID -eq 'SR1415'} | %{ $_.Status = "In Progress" ; $_ } | update-scsmclassinstance

To change a Service Request to ‘Completed’:

(get-scsmclass -name "System.WorkItem.ServiceRequest" | get-scsmclassinstance) | where {$_.ID -eq 'SR1415'} | %{ $_.Status = "Completed" ; $_ } | update-scsmclassinstance

Of course you may want to change other classes in the same way. In order to do this by tweaking the above examples, you will need the class name which you can get using PowerShell like this:

get-scsmclass –DisplayName “Service Request” | select-object name

get-scsmclass –DisplayName “Review Activity” | select-object name

Note: Don’t let Activities catch you out as it’s not System.WorkItem.ReviewActivity as you may initially guess (I did ). Instead it is System.WorkItem.Activity.ReviewActivity

Alrighty, so you end up with something like this to update a service request from completed back to ‘in progress’:

cd C:\program files\Microsoft System Center 2012\Service Manager\Powershell

import-module System.Center.Service.Manager.psd1

(get-scsmclass -name "System.WorkItem.ServiceRequest" | get-scsmclassinstance) | where {$_.ID -eq 'SR1415'} | %{ $_.Status = "In Progress" ; $_ } | update-scsmclassinstance

Great, so now let’s go one better, and make life a lot easier for the SCSM admin folks by creating a custom task that will allow you to click on a service request and do this.

To do this navigate to Library>Tasks and create the task in the following way:

NOTE: By choosing Service Request, this means when my user has a service request selected in the console, the task will appear in the context-sensitive menu on the right –hand side. Therefore obviously if you’ve tweaked this for say a manual activity, then you’ll want to be sure to pick the correct class for which you’re command you’re going to use in the next dialog applies to.

Because we are using the Service Request ID as part of our command, I chose not to select any categories, as the class selection above ensures that when a service request is selected, my task will be available. You may like to use the categories in scenarios where you don’t need to manipulate a specific instance, for instance with a task that closes service requests that are completed for more than 30 days – you may choose to select the Work Item Folder Tasks category in that scenario.

I also chose to log this in the Action log. You don’t really get much in the way of output here as when successful, it just completes without failure, so I chose not to show the output.

The command (for cut and paste purposes) is:

cd ‘C:\Program Files\Microsoft System Center 2012\Service Manager\Powershell’;Import-Module .\System.Center.Service.Manager.psd1;(get-scsmclass -name "System.WorkItem.ServiceRequest" | get-scsmclassinstance) | where {$_.ID -eq '$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Id$'} | %{ $_.Status = 'In Progress' ; $_ } | update-scsmclassinstance

For Manual Activities, you would pick the Manual Activity class instead, and use:

cd ‘C:\Program Files\Microsoft System Center 2012\Service Manager\Powershell’;Import-Module .\System.Center.Service.Manager.psd1;(get-scsmclass -name "System.WorkItem.Activity.ManualActivity" | get-scsmclassinstance) | where {$_.ID -eq '$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Id$'} | %{ $_.Status = 'In Progress' ; $_ } | update-scsmclassinstance

FINAL NOTE: You may not want to make this functionality available to everyone as you don’t want folks breaking all the rules, completing service requests before required activities are completed etc., so through the user roles (Administration >Security), you can narrow down who has access to which task.

Happy Custom Task-ing

Create a Custom Task for Connecting to System Center Configuration Manager 2012 Remote Control from Service Manager 2012 (SCSM) Console

2013-03-08T22:12:12Z

I get asked this almost every engagement I deliver, and there are a lot of great blogs out there talking about how to do this in Config Mgr 2007 / Service Manager 2010 but I always struggle to find one that details how to do this using remote control in Config Mgr 2012 via the Service Manager 2012 console.

So here we go

NOTE: This assumes you have configuration manager set up and agents deployed with the remote control agent enabled. More about that can be found here

First off you can do one of two things:

1) Install the Config Mgr console on machines that have service manager consoles installed, where you intend to run this task from

2) Just copy the contents of C:\Program files (x86)\Microsoft Configuration manager\AdminConsole\bin\i386 (this will be available wherever you have a configuration manager installed) to a directory such as c:\remotecontrol on all machines that have service manager consoles installed.

And then once you have these files in place, you can create a task set up like this in Library>Tasks of the Service Manager console:

General Page:

NOTE: I targeted incident, because the idea here is that I can launch this when clicked on an incident that has an affected configuration item included here (so if it doesn’t work, please check you have something listed here ):

Categories Page (I left mine blank)

Command Line Page:

NOTE: If you have the config mgr console installed on the machine where you’re running the Service Manager console and plan to use this task, the directory shown above is good. If you plan just to copy the contents of the i386 directory around to avoid installing the config mgr console on the machine you’re running the service manager console, then change the directory in the ‘full path to command’ box to the directory that you copied these files too.

NOTE: The ‘Show output when this task is run’ checkbox also needs to be checked in order for the execution of the task to be recorded in the action log.

Here are the values for your cut-and-paste convenience

Command Line Page
Full Path to command:

C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\i386\CmRcViewer.exe

Parameters (optional):

$Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItemAboutConfigItem' TypeConstraint='CustomMicrosoft_Windows_Library!Microsoft.Windows.Computer']/Property[Type='CustomMicrosoft_Windows_Library!Microsoft.Windows.Computer']/PrincipalName$

Working Directory (optional)

%windir%\system32

WHY THIS IS COOOOOL!!

So this showcases the fantastic integration between Config Mgr and Service Mgr, in that when you create a new incident in Service Manager, you choose an affected user. Through Config Mgr’s user affinity feature, Service Manager brings this data into the CMDB, knows the machines associated with the user, and offers them as options in the Affected user CI’s shown in the screenshot above. You can then add one of these and then get remoted in and start troubleshooting right from here:

Happy Remoting!!!!

Cheers, Antoni

System Center 2012 – Service Manager (SCSM) : Useful Links, Guidance and Resources

2013-02-09T06:29:00Z

After all my customer engagements, I tend to share a long list of Links, Resources and Guidance. I though it was waaaayy time that I blogged a list like this, so here it is!

VERSIONS AND UPDATES

List of Build Numbers
http://social.technet.microsoft.com/wiki/contents/articles/4226.list-of-build-numbers-for-system-center-service-manager.aspx

History:
SCSM 2010
CU1 http://support.microsoft.com/kb/983572 (oct 2010)
CU2 http://support.microsoft.com/default.aspx?scid=kb;EN-US;2193861 (oct 2010) 7.0.5826.875
CU3 - http://support.microsoft.com/kb/2390520 (oct 2010) 7.0.5826.886

SCSM 2010 SP1 - http://support.microsoft.com/kb/2484853 (Feb 2011) 7.0.6555.101
CU1 - http://support.microsoft.com/?kbid=2484853 (Feb 2011) 7.0.6555.101
CU2 - http://support.microsoft.com/kb/2542118 (may 2011) 7.0.6555.115
CU3 - http://support.microsoft.com/kb/2588492 (nov 2011) 7.0.6555.128
CU4 - http://support.microsoft.com/kb/2719826 (jul 2012) 7.0.6555.131

SCSM 2012 (7.5.1561.0)
UR1 http://support.microsoft.com/kb/2686249 (May 2012) NO Service Manager Updates
UR2 http://support.microsoft.com/kb/2706783 (nov 2012) 7.0.1561.106
UR3 http://www.microsoft.com/en-us/download/details.aspx?id=34960 (dec 2012) 7.5.1561.116

SCSM 2012 SP1
UR1 - http://support.microsoft.com/kb/2785682 (jan 2013) NO Service Manager Updates

2012 SERVICE PACK 1

What’s new in Sp1
http://technet.microsoft.com/en-us/library/jj614408

My experience of Upgrading to SP1:
http://blogs.technet.com/b/antoni/archive/2013/01/20/my-experience-of-upgrading-to-service-manager-2012-sp1-from-service-manager-2012-rtm.aspx

How Microsoft Upgrade to System Center 2012 SP1 - Service Manager SP1:
http://blogs.technet.com/b/servicemanager/archive/2013/01/23/how-microsoft-upgraded-to-system-center-2012-sp1-service-manager.aspx

SP1 Evaluation VHD
http://www.microsoft.com/en-us/download/details.aspx?id=36427

SETUP AND DEPLOYMENT
Accounts used for running setup:
http://technet.microsoft.com/en-us/library/hh495629.aspx

Infrastructure Planning and Design Guide
Details - http://blogs.technet.com/b/servicemanager/archive/2012/03/26/beta-for-infrastructure-planning-and-design-ipd-guide-for-system-center-2012-service-manager-now-available.aspx
Download - http://www.microsoft.com/en-us/download/details.aspx?id=7

Connector Account Requirements:
http://technet.microsoft.com/library/hh495662.aspx

Disaster Recovery Guide for System Center 2012 - Service Manager
http://technet.microsoft.com/en-us/library/hh495602

Port Assignments
http://technet.microsoft.com/en-us/library/hh495567.aspx

Quick-Start Deployment Guide
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/service-manager-2012-sp1-quickstart-deployment-guide.aspx

SSP Installation
http://www.petri.co.il/self-service-portal-installation.htm

TROUBLESHOOTING ISSUES

Troubleshooting Workflow Performance And Delays
http://blogs.technet.com/b/servicemanager/archive/2013/01/14/troubleshooting-workflow-performance-and-delays.aspx

Data Warehouse / Cube Processing
http://blogs.technet.com/b/thomase/archive/2012/08/27/data-warehouse-jobs-keep-failing.aspx

PERFORMANCE, ARCHITETURE

Why Work Item IDs do not increment uniformly:
http://blogs.technet.com/b/servicemanager/archive/2011/04/06/faq-why-don-t-work-item-ids-increment-uniformly.aspx

Visio Diagram of Data Model
http://blogs.technet.com/b/servicemanager/archive/2011/02/01/model-visio-diagram-released-job-aids-package-update-update-on-resource-kit.aspx

Hardware Performance:
http://technet.microsoft.com/en-us/library/hh519601.aspx

Guidance for Installing System Center 2012 - Service Manager on Virtual Machines
http://technet.microsoft.com/en-us/library/hh495572.aspx

Planning for Performance and Scalability (includes link to job aids which includes sizing helper)
http://technet.microsoft.com/en-us/library/hh495684.aspx

Service Manager Performance
http://technet.microsoft.com/en-us/library/hh519624.aspx

Grooming / Data Retention

This is the best article I know that describes grooming and data retention for the Service Manager DB:
http://blogs.technet.com/b/servicemanager/archive/2009/09/18/data-retention-policies-aka-grooming-in-the-servicemanager-database.aspx

Retention in the Data Warehouse
http://blogs.technet.com/b/servicemanager/archive/2011/06/07/how-much-data-do-we-retain-in-the-service-manager-data-warehouse.aspx

In summary:

When something is deleted (manually or via a connector) it is marked as ‘PendingDeletion’ in the ServiceManager database.
When it is flagged like this, it will not be visible to console users.
It is important to know also that deleting a connector will flag all data that was imported via it, for deletion.
When our grooming job next runs (daily at 3am by default) then the item actually gets deleted from the Service Manager database. Prior to this job running, an object can be restored that was accidentally deleted, using the restore option in the console.
In terms of the Warehouse, this will store all data for 3 years by default, and grooming has to be adjusted manually in the SQL tables for each kind of data, as described in the blog article above.

OUT-OF-BOX CONFIGURATION

Service Manager 101 Focus on Incident Management
http://blogs.technet.com/b/antoni/archive/2012/08/13/service-manager-101-part-1-incident-management.aspx

User Role Permissions
http://technet.microsoft.com/en-us/library/hh495625.aspx

Required SharePoint Permissions for access to SSP
http://technet.microsoft.com/en-us/library/hh495661

User Roles PowerShell Report Using SMLets
http://blogs.technet.com/b/servicemanager/archive/2011/12/01/userroles-powershell-report-using-smlets.aspx

Differences between ‘My Incidents’ and ‘Assigned to Me’ Incident views
Although both of these views will show incidents that are assigned to the logged on user looking at the view, the difference between these views is the columns that are displayed.
The ‘Assigned to Me’ includes SLA-related columns.

Incident vs. Incident (Advanced) Class Use
It is necessary to use the Incident (Advanced) class if it is necessary to base views and queues on criteria involving relationships, for instance a queue showing all incidents where the Assigned To User is empty.
Views created using the ‘Advanced’ class will take longer to load than those using the basic class, due to the amount of data loaded. More detail on this can be found here:
http://blogs.technet.com/b/servicemanager/archive/2010/12/02/faq-why-is-my-custom-incident-view-so-slow.aspx

SLA Management and Notifications
http://blogs.technet.com/b/servicemanager/archive/2012/01/25/scsm-2012-service-level-management.aspx
http://blogs.technet.com/b/servicemanager/archive/2012/02/07/notifying-before-sla-breaches.aspx
http://blogs.technet.com/b/servicemanager/archive/2012/01/25/scsm-2012-import-holidays-in-sla-calendar.aspx

Release Management
http://technet.microsoft.com/en-us/library/hh495636.aspx

Sample helpdesk Scenarios:
http://blogs.technet.com/b/servicemanager/archive/2009/11/02/implementing-sample-helpdesk-scenario-in-incident-management-1.aspx
http://blogs.technet.com/b/servicemanager/archive/2009/11/02/implementing-sample-helpdesk-scenario-in-incident-management-2.aspx

SCENARIO WALKTHROUGHS

Service Manager 101: focus on incident Management
http://blogs.technet.com/b/antoni/archive/2012/08/13/service-manager-101-part-1-incident-management.aspx

Create an Incident on behalf of another user in the SSP (another blog post of mine)
http://blogs.technet.com/b/antoni/archive/2012/06/06/how-to-raise-an-incident-on-behalf-of-a-different-user.aspx

Publishing Announcements to the self-service Portal
http://blogs.technet.com/b/servicemanager/archive/2012/02/22/publishing-service-manager-announcements-to-sharepoint-using-orchestrator.aspx

Importing holidays from Outlook into SLA calendar:
http://blogs.technet.com/b/servicemanager/archive/2012/01/25/scsm-2012-import-holidays-in-sla-calendar.aspx

Publishing Data to a SharePoint Calendar:
http://blogs.technet.com/b/servicemanager/archive/2010/07/02/publishing-work-item-to-part-1-sharepoint-calendar.aspx

Surveys Using SharePoint:
http://blogs.technet.com/b/servicemanager/archive/2009/12/08/incident-resolution-satisfaction-surveys-on-sharepoint.aspx

VIP users:
http://contoso.se/blog/?p=1592

Reset password:
http://contoso.se/blog/?p=3085

Dynamic approval steps in Service Manager with a bit of Orchestrator magic
http://contoso.se/blog/?p=2872

Hide Incident Classification list in SCSM end portal?
http://gallery.technet.microsoft.com/Service-Manager-12-Self-7605e788/view/Discussions

SCSM 2012: Attach file on incident creation
http://scug.be/valerie/2012/04/19/scsm-2012-attach-file-on-incident-creation/

Options for Self Service Software Provisioning:
http://blogs.technet.com/b/servicemanager/archive/2012/04/06/how-to-do-self-service-software-provisioning-with-system-center-2012.aspx
http://blogs.technet.com/b/kghelani/archive/2012/02/06/how-to-redirect-a-request-offering-to-a-request-on-another-site.aspx

Controlling Access to Knowledge Articles
http://blogs.technet.com/b/servicemanager/archive/2010/02/02/how-to-target-knowledge-articles-at-different-groups-of-users.aspx

How to delete items from the Incident Classification List
http://social.technet.microsoft.com/forums/en-us/systemcenterservicemanager/thread/024D4824-8708-4413-AD06-0326EB2D60A2

Deleting work items created for test purposes
http://social.technet.microsoft.com/Forums/en-US/systemcenterservicemanager/thread/92b839bc-dfa5-4760-a9c5-1d11f3f88cfb

Using And / Or Criteria in Workflows and Notification Subscriptions
http://blogs.technet.com/b/servicemanager/archive/2010/11/30/using-and-or-criteria-in-workflow-and-notification-subscriptions.aspx

Change Request and Incident Data passed to Activities
This requires some custom coding and class customization using the authoring tool as described here:
http://garydavidson.net/?p=82

EMAIL INTEGRATION
Out of the box, the following is provided: Incident from incoming email - http://technet.microsoft.com/en-us/library/jj900204.aspx
Outgoing Emails as Work Items are Created / Updated using the workflow / subscription functionality
(For example an incident is assigned to a specific support group like Tier1, so create a subscription to notify a Tier1 DL that a new incident has been assigned to the support group and needs to be individually assigned)

Exchange Connector:
http://blogs.technet.com/b/servicemanager/archive/2012/04/15/exchange-connector-3-0-rc-released.aspx
http://blogs.technet.com/b/servicemanager/archive/2013/02/07/update-on-exchange-connector.aspx

Notify upon Incident / Activity Assignment or Re-Assignment:
http://blogs.technet.com/b/servicemanager/archive/2009/12/15/custom-notification-workflow-on-incident-assignement-or-re-assignment.aspx
http://blogs.technet.com/b/servicemanager/archive/2010/03/12/custom-notification-workflow-on-activity-assignment-or-reassignment.aspx

Creating Notification templates
http://blogs.technet.com/b/servicemanager/archive/2009/09/28/creating-notification-templates-in-system-center-service-manager.aspx

Using Data Properties From the Parent Work Items in Activity Email Templates
http://blogs.technet.com/b/servicemanager/archive/2012/04/03/using-data-properties-from-the-parent-work-items-in-activity-email-templates.aspx

Add Portal URL
http://blogs.technet.com/b/servicemanager/archive/2012/02/13/including-links-to-incidents-or-activities-in-notification-templates-scsm-2012.aspx

Using Mail-Enabled Universal Security Groups (MEUSGs) to notify groups
http://blogs.technet.com/b/servicemanager/archive/2010/09/24/automatically-notifying-groups-of-users.aspx

Use MS Word to Create HTML for notification templates:
http://blogs.technet.com/b/antoni/archive/2012/08/13/service-manager-101-part-1-incident-management.aspx

==================
AUTHORING AND CUSTOMIZATIONS

AUTHORING - TOOLS
2012 RTM Tool - http://www.microsoft.com/en-us/download/details.aspx?id=28726
2012 SP1 Tool - http://www.microsoft.com/en-us/download/details.aspx?id=36214

GENERAL AUTHORING GUIDANCE

What Kind of Skills are Needed to Customize or Extend SCSM
http://blogs.technet.com/b/servicemanager/archive/2010/04/27/what-kinds-of-skills-do-i-need-to-customize-extend-service-manager.aspx

Service Manager 2012 Authoring Guide
http://technet.microsoft.com/en-us/library/hh495563.aspx

CUSTOM VIEWS

Custom Views based on Type Projections (Example - All the incidents assigned to a anybody that is in a particular office or department)
http://blogs.technet.com/b/servicemanager/archive/2010/02/02/creating-views-that-use-related-property-criteria-type-projections-software-views-example.aspx
http://blogs.msdn.com/b/jakuboleksy/archive/2009/01/20/getting-started-with-type-projections.aspx

Creating Views based on User – e.g. a view to show all incidents assigned to a specific user etc. (should help with view by Department too):
http://blogs.technet.com/b/servicemanager/archive/2010/12/02/faq-why-is-my-custom-incident-view-so-slow.aspx

All Work Items Assigned to me View:
http://blogs.technet.com/b/servicemanager/archive/2010/09/28/all-work-items-assigned-to-me-view.aspx

Changing column headers in Views:
http://blogs.technet.com/b/servicemanager/archive/2010/07/21/showing-the-correct-display-name-for-related-objects-in-view-columns.aspx

CUSTOM TASKS

Create a Custom task to reopen incident
http://blogs.litware.se/?p=646

Creating an Incident from a template more quickly (avoiding need to use template picker)
http://blogs.technet.com/b/servicemanager/archive/2011/09/08/incident-quick-templates.aspx

‘Request User Input’ Task
http://blogs.technet.com/b/servicemanager/archive/2009/12/13/requesting-input-from-user-about-an-incident.aspx

Configuration Manager remote assistance task
http://scug.be/scsm/2011/10/24/sccm-remote-assistance-task-in-scsm-console-via-console

MANAGEMENT PACKS

Management Pack Best Practices:
http://scsmguru.wordpress.com/2012/05/10/staying-organized-with-scsm-beware-of-the-management-pack-jungle/

Sealing a Management Pack in System Center 2012 Service Manager
http://blogs.technet.com/b/servicemanager/archive/2012/03/01/sealing-a-management-pack-in-system-center-2012-service-manager.aspx

http://scsmnz.net/sealing-a-management-pack-using-fastseal-exe/

SN.EXE Tool included in Windows SDK Download:
sn.exe http://www.microsoft.com/en-us/download/details.aspx?id=8279

Sealing Management Packs using the Authoring Tool:
http://blogs.technet.com/b/servicemanager/archive/2009/12/25/sealing-management-packs.aspx

FORM CUSTOMIZATION

Good tips on Form Customization:
http://blogs.technet.com/b/servicemanager/archive/2011/01/14/customizing-forms-part-1-adding-a-new-user-picker-control-to-the-incident-form.aspx
http://blogs.technet.com/b/servicemanager/archive/2011/01/14/customizing-forms-part-2-adding-the-affected-user-picker-to-the-change-request-form.aspx

How you can create custom forms using XAML and C# code
http://blogs.technet.com/b/servicemanager/archive/2010/01/08/creating-custom-forms-for-service-manager-using-custom-controls-service-request-example.aspx

Adding Custom Properties to a class and a form:
http://blogs.technet.com/b/servicemanager/archive/2010/05/11/adding-a-custom-property-to-a-form-support-group-property-for-problem-form-example.aspx

Creating Custom Controls for use in forms:
http://blog.scsmsolutions.com/2011/08/create-custom-user-control-for-scsm-2010/

CLASS / PROPERTY CUSTOMIZATION

Add Account Dept ID Property to Windows Computer class:
http://blogs.technet.com/b/servicemanager/archive/2010/09/27/demo-video-how-to-extend-the-data-model-in-scsm-using-the-authoring-tool.aspx

Create a Monitor Class:
http://blog.scsmfaq.ch/2011/01/01/creating-classes/

Add a Customer / Company Class:
http://blog.scsmfaq.ch/2011/01/24/make-service-manager-customer-aware/

Create a Quick Call Work Item class:
http://contoso.se/blog/?p=1827

CUSTOM WORKFLOWS

Creating Workflows with the Authoring tool:
http://blogs.technet.com/b/servicemanager/archive/2009/10/29/service-manager-authoring-tool-the-abcds.aspx

REPORTING AND DASHBOARDS
http://social.technet.microsoft.com/wiki/contents/articles/15608.system-center-service-manager-data-warehouse-and-reporting.aspx

Reports, Dashboards and Cubes
http://www.2013mms.com/digitalmms - Service Delivery & Automation>Service Manager 2012: System Center Data Warehouse, Reporting and Dashboards

POWERSHELL, SCSM CMDLETS, SMLETS

Service Manager Data Warehouse CMDLESTS
http://technet.microsoft.com/en-us/library/hh541724.aspx

Service Manager Administrator CMDLETS:
http://technet.microsoft.com/en-us/library/hh305227.aspx

CODEPLEX SMLETS
http://smlets.codeplex.com/

Using SMlets
http://blog.scsmfaq.ch/2011/01/12/auto-close-resolved-incidents

Changing incident status (automatically closing) with PowerShell Scheduled Tasks
http://scug.be/valerie/2011/12/05/scsm-2012-auto-close-resolved-incidents-after-x-days/

I actually used the script in the comments section of this link to come up with the following:
http://blogs.technet.com/b/servicemanager/archive/2012/05/22/automatically-closing-completed-scsm-service-requests-with-orchestrator.aspx

CD 'C:\Program Files\Microsoft System Center 2012\Service Manager\Powershell'
Import-Module .\System.Center.Service.Manager.psd1
$SomeDaysOld = (get-date).adddays(-3)
$UNC_Now = (get-date).ToUniversalTime()
$IncidentClass = Get-SCClass -Name System.workitem.incident
$Inc_resolved = Get-SCClassInstance -Class $IncidentClass -Filter "Status -eq IncidentStatusEnum.Resolved" | ?{$_.ResolvedDate -lt $SomeDaysOld}
If ($Inc_resolved -ne $null)
     {
     foreach ($Inc in $Inc_resolved)
         {
             $Inc.Status = "bd0ae7c4-3315-2eb3-7933-82dfc482dbaf"
             $Inc.ClosedDate = $UNC_Now
             Update-SCClassInstance -Instance $Inc
         }
     }
Remove-Module System.Center.Service.Manager

Note, the full script at the link Includes Service Requests, but I just wanted to do this for incidents. My above example would close incidents where the resolve date is more than 3 days ago. This can be changed in the third line.
Once you have a script like this, it can be saved and ran as a scheduled task, or you can schedule it to run as a workflow either using the Service Manager Authoring tool or Orchestrator.

Deleting work items created for test purposes
Note in SCSM2012, there is a built-in powershell cmdlet that can be used, removing the need to download and use the smlets from codeplex.
http://social.technet.microsoft.com/Forums/en-US/systemcenterservicemanager/thread/92b839bc-dfa5-4760-a9c5-1d11f3f88cfb

CSV IMPORT

Using the CSV Import Feature
http://blogs.technet.com/b/servicemanager/archive/2009/05/26/using-the-csv-import-feature.aspx

Using a CSV File to Import Data into Service Manager
http://technet.microsoft.com/en-us/library/ff460878.aspx

Importing Users via csv and setting locale and time zone information
http://blogs.technet.com/b/servicemanager/archive/2010/04/12/importing-users-via-csv-and-setting-locale-and-time-zone-information.aspx

Another CSV import Example
http://scug.be/blogs/scsm/archive/2009/12/16/importing-data-into-scsm-part4-the-manual-amp-csv-import-ci-creation.aspx

SELF-SERVICE PORTAL (SSP)

Customizing the SCSM 2012 Self-Service Portal–How do I change the “Need Help?” or Description Text?
http://blogs.technet.com/b/servicemanager/archive/2012/02/06/customizing-the-scsm-2012-self-service-portal-how-do-i-change-the-need-help-or-description-text.aspx

Customizing the self-service portal to have a generic request point to a service request rather than an incident:
http://blogs.technet.com/b/servicemanager/archive/2012/02/13/changing-the-generic-request-in-portal-to-point-to-service-request-template.aspx

Customize the SSP Portal Header:
http://blogs.technet.com/b/servicemanager/archive/2012/05/10/faq-how-do-i-customize-the-smportal-header-on-the-portal-to-something-else.aspx

How to Write a Custom Webpart using Service Manager Base Webpart
http://blogs.technet.com/b/servicemanager/archive/2012/02/07/how-to-write-a-custom-webpart-using-service-manager-base-webpart.aspx

How to Deploy Service Manager Webparts to an Existing SharePoint Site
http://blogs.technet.com/b/servicemanager/archive/2012/01/27/how-to-deploy-service-manager-webparts-to-an-existing-sharepoint-site.aspx

Part I - Custom Silverlight module for Service Manager 2012 portal
http://blogs.technet.com/b/servicemanager/archive/2012/01/05/custom-silverlight-module-for-service-manager-2012-portal.aspx

SYSTEM CENTER CONNECTORS / INTEGRATION

SCCM, SCSM and Primary User
The Primary User field is populated based upon the User Affinity data which is automatically brought in by the Configuration Manager connector. This has the effect of displaying default CIs for selection, when picking an affected user:
Setting up User affinity resources:
http://technet.microsoft.com/en-us/library/gg699365.aspx
http://technet.microsoft.com/en-us/video/Video/hh550076

Configuration Manager remote assistance task
http://scug.be/scsm/2011/10/24/sccm-remote-assistance-task-in-scsm-console-via-console

Enabling Asset Intelligence in Configuration Manager to populate Software Inventory Details:
Asset Intelligence in Configuration Manager: http://technet.microsoft.com/en-us/library/cc161988

Application Approval Workflow Solution Accelerator
This is a Solution Accelerator available from Microsoft which provides required integration pieces for config Mgr, Orchestrator and Service Manager 2012 in order to allow end users to request software via the Config Mgr application catalog, and for Service Manager to

track and control the approval process.
Download - http://www.microsoft.com/en-us/download/details.aspx?id=29687
Demo video - http://blogs.technet.com/b/servicemanager/archive/2012/04/05/demo-application-approval-workflow-aaw-solution-accelerator.aspx

Working with Orchestrator and Relationships
http://blogs.technet.com/b/servicemanager/archive/2012/05/22/working-with-relationships-in-the-scsm-orchestrator-integration-pack.aspx

Orchestrator and Service Manager Integration Training:
https://www.microsoftvirtualacademy.com/tracks/system-center-2012-orchestrator-service-manager

Real World Examples of Service Manager and Orchestrator Integration
http://blogs.technet.com/b/servicemanager/archive/2011/11/10/demo-automating-service-request-fulfillment-from-the-scsm-service-catalog-with-orchestrator-real-world-examples.aspx

FAQ: why don’t new folders / Runbooks show up in SCSM?
http://blogs.technet.com/b/servicemanager/archive/2012/04/22/faq-why-don-t-my-new-folders-runbooks-show-up-in-the-scsm-orchestrator-connector.aspx

Runbook Statuses in Service Manager
http://blogs.technet.com/b/servicemanager/archive/2012/02/21/runbook-statuses-in-service-manager.aspx

Using Orchestrator
http://blogs.technet.com/b/servicemanager/archive/2012/05/22/automatically-closing-completed-scsm-service-requests-with-orchestrator.aspx

How to Import Management Packs for System Center Operations Manager Configuration Item Connectors
http://technet.microsoft.com/en-us/library/hh519707.aspx

Network device import
http://blogs.catapultsystems.com/cfuller/archive/2012/07/13/how-do-i-integrate-operations-manager-2012-network-devices-into-service-manager-2012-as-configuration-items-%5Bscsm-scom-sysctr%5D.aspx

3RD PARTY ADD-ONS
Cireson - http://www.cireson.com/
Provance - http://provance.com/
GridPro - http://www.gridpro.se/en/

TRAINING AND CERTIFICATION

Private Cloud MCSE Certification
http://www.microsoft.com/learning/en/us/certification/cert-private-cloud.aspx

Private Cloud Jump Start Training
http://technet.microsoft.com/en-us/video/private-cloud-jump-start-02-configure-and-deploy-infrastructure-components

Microsoft Virtual Academy Training
http://blogs.technet.com/b/servicemanager/archive/2012/06/08/free-training-microsoft-virtual-academy-course-for-service-manager-2012.aspx

PRIVATE CLOUD

Private Cloud Demo Extravaganza Videos!
http://blogs.technet.com/b/orchestrator/archive/2012/05/22/private-cloud-demo-extravaganza-videos.aspx

Session Recordings and Slide decks from Microsoft Management Summit 2012
http://www.mms-2012.com/digitalmms

EVENTS / USER GROUPS

MMS (Microsoft Management Summit)
MMS is our annual System Center / Manageability Conference that we have held historically either in Las Vegas or San Diego.
The links to the recordings of the 2012 sessions together with the opportunity to register for MMS 2013 can be found at the MMS 2013 website:
http://www.2013mms.com/

BLOGS

System Center Community Wiki Page
http://blogs.technet.com/b/servicemanager/archive/2012/06/06/new-how-to-participate-in-the-system-center-community-wiki-page.a

My Experience of Upgrading to Service Manager 2012 SP1 from Service Manager 2012 RTM

2013-01-20T06:22:00Z

Last week, System Center 2012 SP1 became generally available – Download, New Features and release Details available here. The day after release, I assisted a customer in upgrading successfully from System center 2012 – Service Manager to System Center 2012 SP1 – Service Manager, and I wanted to share my observations together with some tips and guidance to help others with upgrading.

Good luck with your upgrade!!!

Important Notes

1) DO NOT ATTEMPT to update multiple management servers simultaneously. Allow the DWMS to complete, before moving onto a MS. There is a known issue doing this with SCOM Management servers, and although I have not ran into the same issue yet with SCSM (yet ) , I would not risk it for the trade off of letting each Management Server complete, before moving on to the next Management Server

2) The Data Warehouse Management Server is updated BEFORE the Service Manager Management server – This is the opposite to how you would’ve installed the product originally.

3) If you have other System Center Components, please note the Suite component Order as described at this link:

http://technet.microsoft.com/library/jj628203.aspx

4) Service Manager (and in fact all of the System Center 2012 components) must be at System Center 2012 Update Rollup 2, before you can do an in-place upgrade to 2012 SP1

5) Make sure you have everything backed up (mainly the encryption keys, all databases and all unsealed management packs) that you may need, should things not go quite according to plan (it happens occasionally, right?! ). Details about Preparing for a DR situation can be found here: http://technet.microsoft.com/en-US/library/hh524274.aspx

6) You will need SQL 2012 analysis Management Objects (listed on this page as Microsoft® SQL Server® 2012 Analysis Management Objects) on the management servers. There will be a link to this in the SP1 update pre-requisites checker, but, if you install the Analysis Management objects from there, you will need to restart the upgrade setup rather than just re-check, in order for the pre-requisite checker to pick it up (and this would mean you re-entering your product key again) so best just to get it on, before you even start.

7) There is one media which is used both for brand new 2012 SP1 installs, and in-place upgrades.

8) Be sure to look at ALL the documentation, as it is spread out over different links, and different steps apply to different situations and environments. The intent of this blog is to bring some of this together. Here are the docs to look at:

Upgrading System Center 2012 – Service Manager to System Center 2012 SP1 – Start here to check the order of upgrade if you have other components of the System Center 2012 suite like Ops Mgr, Config Mgr, Orchestrator etc.

For more detail on this, be sure to check the Upgrade Sequencing for System Center 2012 SP1 link and please note that on the left hand side in the navigation bar, you will see a link for each component outlining suite compatibility notes and considerations. For instance, here is the one for Service Manager

Next take a look at the Upgrade Planning for System Center 2012 – Service Manager link and the sub-pages shown on the left navigation tree about upgrading the self service portal, connectors and the reporting DLL on the remote SQL Server Reporting Service

Next go to the Upgrade to System Center 2012 SP1 – Service Manager link which links to How to prepare a Service Manager 2012 for Upgrade to Sp1 and the How to Upgrade to System Center 2012 Sp1 – Service Manager pages.

Once you’re done with your successful upgrade, you will want to take a look at this page – After Upgrading to System center 2012 SP1 – Service Manager to take care of post-install tasks.

The Failed Upgrade in System Center 2012 SP1 – Service Manager page will give you some tips if anything goes wrong along the way.

OK, so taking all of the above into account, these are the steps I came up with (which may need to be adapted for your scenario / environment)

Generic High-level steps for an SP1 upgrade:

NOTE as described above Orchestrator should be upgraded prior to Service Manager.

1) Prepare for upgrade by disabling DW jobs and confirming they have stopped running:

http://technet.microsoft.com/en-us/library/jj900186.aspx

2) Remove any 2007 R2 or 2012 SCOM agents on any of the management servers (a compatible SCOM 2012 agent will be installed as part of the SP1 upgrade)

3) Copy new 2012 SP1 Reporting DLL (if SSRS is remote to DWMS):

http://technet.microsoft.com/en-us/library/jj900198.aspx

4) Upgrade DW MS

5) Upgrade MS

6) Upgrade Console(s)

http://technet.microsoft.com/en-us/library/jj900202.aspx

7) Restart dw jobs and complete post-install steps:

http://technet.microsoft.com/en-us/library/jj900190.aspx

8) Upgrade Self-Service Portal

Basically an in-place upgrade: http://technet.microsoft.com/en-us/library/jj900201.aspx.

9) Configure SCOM agents to report to the SCOM Server (if applicable)

My experience and observations

With my first upgrade from 2012 to 2012 SP1 (at a customer site ), we had the following environment (Note the steps may be different depending on where you have various components installed)

4 Servers (not the real names of course!!):

SMMSSQL (Service Manager Management Server, SQL hosting ServiceManager)

DWMSSQL (Data Warehouse Management Server, SQL hosting DW databases. SQL Reporting Services)

SMSSP (Web Content Server)

SHAREPOINT (SharePoint Web parts)

High-Level Plan

So this is the high-level plan I came up with, and the one that we followed (detail and observations from each step below) :

1) Ensure DR / backups are taken care of.

2) Prepare for upgrade by disabling DW jobs and confirming they have stopped running:

3) Upgrade DW MS

4) Upgrade MS

5) Upgrade Console(s). Remember your consoles would need to go to UR2 prior to being updated to 2012, so another option is to just uninstall the 2012RTM console and then install a 2012 Sp1 console using the media.

6) Restart dw jobs and follow post-install steps.

7) Upgrade SSP

Detail of these Steps and Observations along the way

1) Ensure DR / backups are taken care of.
Same as Important Note 5 at the top of this article:

Make sure you have everything backed up (mainly the encryption keys, all databases and all unsealed management packs) that you may need, should things not go quite according to plan (it happens occasionally, right?!). Details about Preparing for a DR situation can be found here: http://technet.microsoft.com/en-US/library/hh524274.aspx

2) Prepare for upgrade by disabling DW jobs and confirming they have stopped running:

This documentation calls for running the Service Manager Shell, but On My DWMS, there was no Console or Service Manager Shell, so instead we ran Windows PowerShell (need to run as Administrator so that the execution mode can be set) and then we were able to run all of the other commands. In the ‘After upgrade’ steps, it tells you to run the PowerShell commands through windows Powershell.

The jobs did not show as ‘Disabled’ anywhere, but they continued to show as ‘not running’ after a number of refreshes so this was good enough for me.

NOTE: It may be worth leaving your PowerShell window open when done, as you will be running the same commands but with ‘enable’ instead of ‘disable’, post-upgrade.

3) Upgrade DW MS

4) Upgrade MS

Steps 3 and 4 were pretty straight-forward following these steps:

5) Upgrade Console(s). remember your consoles would need to go to UR2 prior to being updated to 2012, so if your consoles are not yet at UR2, another option to consider is to just uninstall a previous version’s console, and then install a 2012 Sp1 console using the media.

6) Restart DW jobs and post-install steps:

In my case, the services were already started. The services will be automatically restarted as part of the update. Definitely worth checking that they came back up though! This time the documentation does have you go through windows PowerShell to restart the jobs.

7) Upgrade SSP

This is just a case of running through the upgrade both on the web content server (IIS server hosting the portal) and the SharePoint Web parts server. Bear in mind however that the IIS services will be restarted so if the web parts SharePoint server hosts other sites, this may cause a very brief outage.

Service Manager 101 - Focus on Incident Management

2012-08-13T21:31:00Z

System Center 2012 - Service Manager 101: Focus on Incident Management

System Center 2012 - Service Manager (SCSM) includes Incident Management, Service Request fulfillment, Problem Management, Change Management, Release Management and Activity Management out of the box. Most Customers like to start with Incident Management. During my engagements out at customers (I am a Premier Field Engineer with Microsoft) I often hear of the need for a guide like this which pieces together all the initially required configuration. Therefore I created this guide, and included many of the tips, best practices and additional guidance that I recommend to the customers I assist. As time allows, I hope to produce similar guides like this for other areas of the product like Service Request Fulfillment. Any feedback, suggestions for new posts, or comments greatly appreciated.

TERMINOLOGY

In order to understand how to effectively configure Incident Management in Service Manager, there are some key terms that are helpful to understand, especially if you're brand new to Service Manager.

An extensive official Microsoft Glossary is available here

Below are my personal definitions of some of the most significant terms for Service Manager, and in particular Incident Management:

Configuration item - An object such as a User or Computer, Service, Software Update, Printer etc. and other types of object.

Work Item - An item that is worked on such as an Incident, Service Request, Change Request, Problem or Activity.

Queue - This is one of the concepts that can be one of the most confusing in Service Manager, due to the differences with how Queues are implemented in other incident management systems. In Service Manager, it is best to think of a queue as the criteria itself that defines a logical group of work items (such as incidents). An example of a queue in Service Manager would be 'All priority 1 Incidents'. This becomes important when working with the contents of a queue. For instance, when creating a view in Service Manager, there is no option to select a specific queue to display the incidents that it refers to. Instead you create a view and set the same criteria as you defined for the queue. Although a queue cannot be picked and selected as the basis for a view, there are other reasons why it is important to define queues:

SLAs (Service Level Agreement

User Role
Escalation / transfer Purposes

NOTE: Do not confuse Queue with 'Incident Tier Queue' which is the name of the list used to define 'Support Group' values like tier 1, tier 2, tier3, helpdesk, infrastructure team etc. There is more about this in the Support groups Section below.

Group - A group of Configuration Items such as a group of Computers / Users. An example would be a group called ‘Production Exchange Server’s that contains the computer records of all the Production Exchange Servers

NOTE: A Group is a group of Configuration Items, A Queue is a group of Work Items

Support Group / Incident Tier Queue - This is a group of people that work on work items, for instance

Tier 1

Tier 2

Tier

Exchange group

App Group

SQL DBAs

Helpdesk

Field Technician

Infrastructure Team

Or you might have combinations of these such as:

Tier 1 Helpdesk

Tier 2 Helpdesk

Tier 1 Exchange

Tier 2 Exchange etc..

You can even create Parent and Child Subgroups such as:

Infrastructure

Infrastructure\Network

Infrastructure\Exchange

Infrastructure\Active Directory

OVERVIEW OF THIS GUIDE

Alright, so now you have the key terminology down, how do you get a working incident management system, configured to your organizations needs?

The rest of this blog post will walk you through 19 key areas to help get the incident management system up and rolling. I suggest each of these configuration sections are followed in the order that I lay them out below, as configuration and customizations carried out in preceding sections will be used in the following sections.

Here is an overview of the sections that follow:

1) Configure Connectors (Active Directory, System Center Configuration manger, System Center Operations Manager, System Center Orchestrator)
2) Create a Custom Management Pack
3) Review and Configure Incident Classifications
4) Configure Email channel Settings
5) Review and Configure Support Groups
6) Configure Impact and Urgency
7) Configure Incident Settings
8) Create (Incident) Templates
9) Create Queues
10) Create Views
11) Configure Notification Templates
12) Configure Subscriptions
13) Configure Workflows
14) Add Functionality to Notify on assignment/ re-assignment
15) Create Service Level Objectives (SLOs)
16) Create User roles
17) Configure Incident Creation from Email
18) Initial Configuration of Self-Service Portal (SSP)
19) Knowledge Base Integration

OPTIONAL 1) Create your own Incident Request Offering, allowing customization of the incident form on Self-Service Portal
OPTIONAL 2) Create Request Offering to allow users to raise incidents on behalf of other users
OPTIONAL 3) Enhance your Email notifications sent out by Service Manager

DETAILED GUIDE

TIP: Most of the time when you create customizations and configuration changes, you will be presented with a Summary page before you click Create. If it is desired to document the configuration and customizations (which is often a good idea :-), the contents of these Summary pages can be copied and pasted.

1) Configure Connectors

(Active Directory, System Center Configuration manger, System Center Operations Manager, System Center Orchestrator)

Background: Configuring the Connectors is important because when you raise an incident, you want to be able to pick the affected user and affected / related configuration items from data that has been imported from the system. Most people start with the AD connector to bring in basic information like User and Computer Data. Configuration Manager gives some big added bonuses for Incident Management. For instance, when you pick an affected CI (computer) all the hardware / software data will be present:

NOTE: In order for the software to appear, it is necessary to configure asset intelligence, as described here:

Another big advantage of connecting configuration manager is that when you raise an incident in the console and pick an affected user, it will show the possible configuration items that user is known to be a primary user of (which is also determined by configuration Manager based on logon frequency etc., and brought in via the Config Mgr connector)

Steps for setting up each of the connectors can be found here.

The requirement for accounts used for connectors can be found here

TIP It is Best Practice to specify a separate account for each connector. Connectors each run under separate monitoringhost.exe processes in task manager, so specifying a different account per connector will assist in determining which process is running which connector. This can be especially useful for troubleshooting purposes.

2) Create a Custom Management Pack (MP) and decide a naming convention

A custom management pack starts out as an empty bucket (xml file), within which much of your configuration and customization will be stored. In most cases, one of the management packs supplied with the product will be suggested as the default container to store a configuration / customization in. For instance, when you create an incident template, the default option for the MP to store it in is the Service manager Incident management Configuration Library:

It is best practice to store your configurations and customizations in a custom management pack (MP). Here is why:

Helps distinguish your configuration and customization changes (such as your custom templates) from the ones included out of the box

Makes it easier to find you custom elements in dialogs, views etc. (using the 'find' / 'look for' functionality and the ability to sort using your convention).

Prevents extra dependencies being created on other management packs

Sometimes you may want to run manual SQL queries against the DB and it can be easier if you can narrow the query down using the managementpack ID, part of the MP name or part of the element (such as template) name.

TIP: Consider grouping particular customizations into specific custom MPs. For instance one of my blogs walks you through creating an incident on behalf of a user and it may be preferable to define all the configuration for this in a specific MP. This way it is easy to re-use the specific customization in other environments, or rip it out if you need to clean up or decide you no longer want this functionality.

TIP: Strongly consider using a naming convention also such as a short prefix. For example I prefix all my customizations with Antoni. Whenever you create a notification template, call it something like Antoni Notification template for Notifying End User of resolution. This is useful for distinguishing and makes it easier to find customizations as described above.

TIP: One more tip with naming and description - put as much information into the name as possible making it easy to figure out what a customization is for just by looking at the name, and use the description field. For instance if you create a Review Activity template that has 2 reviewers in it called Antoni H and Emmett H, then a bad name would be 'Review Template 1’ A good name would be:'Antoni review template containing approvers Antoni H and Emmett H - unanimous'.

3) Review and Configure Incident Classifications.

Think of Incident Classifications as your types of incidents. A good way to start thinking about this is to think of incidents that are raised in your environment, how you would categorize some the most commonly raised incidents, and whether you need to sub-categorize for classification and reporting purposes.

This can becomes a trade-off between having very granular classifications for reporting / analyst purposes but then keeping it simple for End Users raising incidents from the Self-Service portal (as by default they will see the entire list of incident classifications when they go to raise an incident in the portal).

One great way of getting round this trade-off, is to create a new Incident Template, and then create a custom Request Offering based on it. In the Request Offering you can then choose which fields the user will see on the incident form. This allows you to hide the classification. Additionally, you can set a default in the template. And you may want to create and use a placeholder category such as SET BY ANALYST). Then for the end user incident entry, you could just offer a title (brief description), description (detailed) and opportunity to attach a file like shown below:

More detailed steps for doing this can be found in the optional 1 section, at the bottom of this post.

A number of Incident Classifications are provided out of the box, but these can be added to or reconfigured as needed in the Library>Lists>Incident Classification section of the console.

4) Configure Email channel Settings

This Setting will designate the server and return address that Service Manager will use for outgoing emails. For instance if you configure a subscription to send an email when an SLA is about to breach, or if you configure a workflow notification to send an email when a new incident is created for a given support group (such as an incoming helpdesk) this is the email server that will be used, and the email address that the email will come from. The address used here does not require a mailbox, so something like helpdesk-DoNotReply@contoso.com is valid.

To configure these settings, navigate to Administration>Notifications>Channels, double click email notification channel and configure the Server name and return address.

In my environment, I also checked Windows Integrated, rather than anonymous as this was required for my Exchange configuration

More detail on which setting to use can be found in this blog post, but check with your Exchange Administrator if you are unsure which setting to use.

5) Review and Configure Support Groups (a.k.a Incident Tier Queues)

Note, in the vast majority of places, you will see Support Groups called just that in the console, but the one place you will see them referenced with a different name is in the Library>Lists section where the list is titled 'Incident Tier Queue'.

Support Groups (a.k.a Incident Tier Queues but will be referred to as Support Groups from here on in) are the groups of people / teams that work on Incidents.

NOTE: The 'Service Request Support Group' list is for Service Request work items, rather than incident work items and is completely independent to the 'Incident Tier Queue' (Incident Support Group) List.

Here are some implications of Support Group configuration

The 'Support Group' field can be (and is often) used to wholly or partly define Queues. In a small environment (or as part of an initial configuration), it may make sense to create queues that mirror the Support Group List. For example:

Support Group	Queue
helpdesk	Incoming Queue
Tier 1 Group	Tier 1 Queue
Tier 2 Group	Tier 2 Queue
Tier 3 Group	Tier 3 Queue
Infrastructure Team	Infrastructure Team Queue

When a Queue is created, you can select the Support Group as matching criteria like this:

Support Groups can be used to define views - You may define your views based on the selected support group. This way you build a view showing all incidents with a given incident support group specified.

A Support Group can be specified in a template - As described above, you may have an incident support group that always deals with a particular genre of incidents, for example printing incidents (e.g. Tier 1 or Tier 1 - Printing). Therefore you can create a 'printing Incident' template, and specify the Support group that handles Printing Incidents in the template. The template can then be applied manually or automatically to set the value of the support group. (see section 8 below for more on this) As a result, the Incident now matches any queue / view criteria specifying the selected support group.

Each support Group could have an associated distribution group that can be used in subscriptions - Once support groups are defined as needed, subscriptions could be created so that when a support group is set to Tier 1 Printing for example, an email is sent to the 'Tier 1 Printing' Distribution group. More on setting a subscription like this up can be found in section 12 below)

If you wish to follow along with the exercises in the following sections, create 2 additional support Groups using the following steps:

5a) navigate to Library>Lists>Incident Tier Queue

5b) Click Add Item.

5c) Scroll down and find the newly added 'List Value’.

5d) Click ‘List Value’ to highlight it

5e) In the name box, highlight the words ‘List value’ there and overwrite it with the Support Group name such as Helpdesk or Infrastructure Team.

NOTE: You will also come across the "escalated' checkbox in the incident form. This can sometimes be useful to include as criteria for SLAs, Queues, workflows and Subscriptions. When you use the 'Escalate or Transfer' task on the right-hand side, the option is available to set this field to true:

6) Configure Impact and Urgency

In Service Manager, the Impact and Urgency fields are defined as follows, out of the box:

Urgency:

Medium

High

Impact:

Medium

High

These can be changed / added to or reduced as necessary. The priority field is calculated automatically based on the combination of these fields as described in the next Section.

If you wish to change these values (not required for any of the exercises in this guide) use the following steps:

6a) navigate to Library>Lists>Urgency or Library>Lists>impact

6b) Click Add Item.

6c) Scroll down and find the newly added 'List Value’.

6d) Click ‘List Value’ to highlight it

6e) In the name box, highlight the words 'List value' there, and overwrite them with the Urgency or Impact value you wish to use such as 'Minimal' or 'Mission Critical'.

7) Configure Incident Settings

In Administration>Settings>Incident Settings, the following settings can be configured:

General Page

Default Support Group: This is the default support Group that will be set for the incident if one is not specified either manually or via a template.

Parent Incident Page

Allows you to control the behavior of parent>child incidents. The level of control offered here (child incidents - Parent incidents) is more granular than that offered with incidents linked to problems.

NOTE: When a problem is resolved, the option is available to resolve any incidents associated with the problem.

Priority Calculation Page

This is where you determine the priority that will be set, based on the impact and urgency set. If you customized the Impact and Urgency Lists as described in the previous Section, you will see your new values displayed here.

Note mine are set as shown here, but by default the grid is blank to allow you to set this up as required.

Resolution time page

This can be mostly disregarded as this was what we used in Service Manager 2010 prior to the new 2012 Service Manager SLA functionality being introduced. This is why there is a checkbox to disable this functionality which will prevent the resolution time showing in an incident banner.

If you plan to use the new 2012 functionality, I recommend checking the 'Do not use and show legacy Target Resolution time on Incident Form banner' box to disable this 'legacy' option

Operations Manager Web console Page

This is important when you integrate Operations Manager with Service manager and have incidents raised from alerts. This will enable the following tasks to navigate to the appropriate alert or place in health explorer that shows the problem from the Operations Manager perspective:

NOTE: You will only see these tasks when you click on an incident in that was raised by the operations manager connector

Incoming Email Page

This allows you to enable incoming emails to be converted into incidents. This is achieved by creating an IIS SMTP virtual server, and then in exchange by creating a rule that forwards all emails sent to a given address (like helpdesk@contoso.com) to the IIS virtual server. Service Manager watches the SMTP virtual server and converts emails found in the drop mail box location into incidents. Steps for setting this up can be found here:

Note for more Advanced Email Integration, the Exchange Connector is available:

Please note that the Exchange Connector is currently not supported by Microsoft.

8) Create (Incident) Templates

Templates are a great feature of Service Manager and help save time, whilst providing consistency where appropriate, between your work items. If you click Create Incident, it will open up a brand new Incident form like this:

If this seems like an overwhelming number of fields to fill out, or this becomes repetitive for commonly occurring types of incident, this is where templates help, in pre-filling a number of these fields out for you, consistently and automatically. For instance from the above screenshot, if I click Apply Template on the right-hand side and choose the 'Antoni Printing Incident Template', it will fill out the fields for me as shown below:

TIP: Another consideration for your templates is using prompts in your template as shown above in the description field.

Once you have templates defined there are some cool things you can do with them:

For an existing Incident, Apply a template using the 'Apply template' task as described above

Create a brand new incident from a template using the 'Create Incident from Template' task.

Apply templates automatically in workflows. For example a workflow could watch for incidents raised from the portal with the 'Printer Problems' incident classification and then automatically apply a template like the 'Antoni Printing Incident Template' example described above.

Create a brand new incident from a template using the 'Create Incident from Template' activity in System Center 2012 - Orchestrator.

Many customers have also found this link of interest before which allows quick-step incident creation from templates

A good incident template to start with is a 'default' Incident template for your organization. If an incident comes in via email or portal, you may want a configuration like this:

Priority - Low,

Urgency - Low,

Support Group = Help Desk

Incident Classification = 'Set by Analyst’

The template would look like this:

In section 13 (Creating workflows) below, you will use a workflow to automatically apply this template for incidents coming in via email or the portal.

9) Create Queues

Your Queues will be needed for the following

SLAs - These are applied to Queues

User Roles - For security and Views, User Roles can be scoped down to certain queues so that certain users (belonging to a user role) only see the work items that match the queue criteria.

In addition to specifying more obvious criteria for queues such as 'Incident Classification' (like Printing Problems) or 'Support Group' (such as Tier 1), you may like to combine these or create additional queues, such as the following examples:

Priority 1 Incidents - This will come into play in SLOs if say you created an SLO for the time it takes to resolve a Priority 1 incident.

Priority 1 Incidents to be assigned.

Priority 1 Incidents Assigned to Helpdesk.

Queues are created in the Library> Queues node.

The work Item type can be any of the work items such as incident, change request, activity etc..

But in this case we will use Incident

BUT WAIT!!! There is something that may be not completely obvious here, which is that you may want to use the Incident (Advanced) class. This is true for example if you want to create an 'unassigned' queue (which is how many people typically think of a 'queue' in incident management systems).

Using Incident (Advanced) gives access to relationships, such that when you get to the criteria, you can drill down into classes related to the incident (such as Assigned to User) and then set the queue up with criteria like Assigned to User Username is empty. Here is an example of this:

NOTE: The little arrow to the left hand side of Incident is only visible when you choose a combination class like Incident (advanced). You will not see that if you just choose Incident.

Exactly the same principle applies to when you create your views, in that may need to use the 'Incident (advanced)' class, for instance if you want to create a view showing only unassigned incidents, which will be discussed in the next section. Before creating everything you do with the advanced class though, please be aware it takes longer for the views to load, as described here

For now we will create 3 Queues:

All incidents (will be used in the SLA section later on).

All Infrastructure Team incidents (will be used in the views and User roles sections).

All priority 1 incidents (will also be used in the SLA section later on)

Create the "All Incidents' Queue:

9a) Navigate to Library>Queues

9b) On the right hand side in the task pane click Create Queue

9c) give the Queue a name. I will use ‘Antoni - All Incidents’

9d) In the Work Item type, click browse and select Incident

9e) change the MP to one of your custom MPs (I will use my Antoni Custom MP) and click Next

9f) In the Criteria page, leave the default of nothing selected and click Next

9g) click Create and then close.

To create the "All Infrastructure Team Incidents" Queue

9a) Navigate to Library>Queues

9b) On the right hand side in the task pane click Create Queue

9c) give the Queue a name. I will use ‘Antoni - All Infrastructure Team Incidents’

9d) In the Work Item type, click the '...' button and select Incident, then click OK

9e) change the MP to one of your custom MPs (I will use my Antoni Custom MP) and click Next

9f) In the Criteria page, in the Available properties box, start typing Support Group, check the Support Group box, click Add.

9g) leave the default of Equals selected and then in the red box select Infrastructure Team from the dropdown.

9h) click next, then Create, and then close.

To create the "All Priority 1 Incidents" Queue

9a) Navigate to Library>Queues

9b) On the right hand side in the task pane click Create Queue

9c) give the Queue a name. I will use ‘Antoni - All Priority 1 Incidents’

9d) In the Work Item type, click the '...' button and select Incident, then click OK

9e) change the MP to one of your custom MPs (I will use my Antoni Custom MP) and click Next

9f) In the Criteria page, in the Available properties box, start typing Priority, check the Priority box, click Add.

9g) change the 'less than' to Equals and then in the red box type 1. It should look like this:

9h) click next, then Create, and then close.

10) Create Views

A number of useful views are provided out of the box in the work Items>Incident Management area of the console. If you have completed some of the customization described above (like creating queues, support groups etc.), then you are likely to want to create some of your own views.

Many times you will want to use relationships to determine the contents of a view. For example, to show all unassigned incidents, you could set up a view using the 'Incident (Advanced); class and then specify Assigned to User, username 'is empty'.

However although this will achieve your objective, views based on the Incident (Advanced) class may be slow to load. This is where the 'Incident (typical)' type projection can help as it loads a lot less related items that the Incident 'advanced' class.

The one consideration of using this class is that because it is in an unsealed Management Pack (the MP), you cannot reference it in another Unsealed MP (such as your own Custom MP that you may be storing all or some of your customizations in. Therefore the way round this is to re-create the type projections in your Unsealed custom MP where you will be storing the views or queues that use these type projections. More detail and the sample code required to do this is available here. This requires some custom xml editing, but you will likely find the performance improvements makes the time investment worthwhile (and your analysts using these views a lot happier :-)

Initially you may like to start out using the Incident (Advanced) class, but just be aware of this performance consideration.

11) Configure Notification Templates

There is a strong likelihood that you will want users to be notified in situations such as the following:

Notify a helpdesk or support group that handles incoming incidents when a new incident is created

Notify an end-user that their incident has been resolved.

Before Creating these subscriptions, it is a good idea to create notification templates. The notification template will determine what is in the subject and body of an email sent by a Service Manager Subscription.

So for instance, in your email sent to the helpdesk, you would need it to say something like Dear helpdesk, a new incident has been created for the helpdesk with the following details. And then there may be a table showing appropriate fields like this:

For the email sent to an end user confirming resolution you would want something like, Dear [end-user first name] your incident has been resolved. And then maybe a table containing different fields.

So this means that you need a different notification template for each of these scenarios.

NOTE: Notification Templates are stored under Administration>Notifications>Templates, NOT under Library>templates with the 'work items' templates

TIP: Have a basic Notification Template just with the word 'test' in the subject line or body and use this when you initially create a subscription / or workflow that sends a notification. This will allow you to test the workflow / subscription functionality, ruling out any potential problems with the template. This is especially helpful when you start adding variables to templates and are unsure if the variables are not appearing correctly or something else with the template is preventing the notification from being sent.

TIP: If you use HTML, don't forgot to check the 'Send as HTML' check box

TIP: If you're not proficient in HTML, you can let Microsoft Word do a lot of the work for you by creating a word doc with a table for example, and then save the document as a web page. Once you have the HTML, you can paste it into the notification template, stripping out anything not needed and replacing the placeholders you created with the actual variables, using the insert button. This is described more in the Optional 3 section of this blog post.

TIP: Create Generic Notification Templates where possible. For example instead of creating a notification template that says 'A new incident has been placed in the tier 1 Queue', create one that says 'New Incident in Queue'. This way notification templates can be more likely reused in multiple subscriptions / workflows.

Steps to Create a Test Notification Template

11a) Go to Administration>Notifications>Templates.

11b) On the right-hand side click 'Create Email template'

11c) Give the template a name. I will call mine ‘Antoni Test - Test in Subject and Body – Incident’

11d) Under Targeted Class, click Browse and Choose Incident

11e) Change the MP to a Custom MP. I will use Antoni Custom MP

11f) In the template design type the word 'test' in the Message Subject and also in the message body

11g) Click Next and then in the Summary page, click Create.

Steps to Create a Notification template for Incident in Q

11a) Go to Administration>Notifications>Templates.

TIP: You can either create a new template from scratch, or there is an option on the right to Duplicate so you can use one of the out of the box templates as a starting point. In this exercise, we will duplicate and re-use the out of the box 'Assigned To User Notification template' This will give you the Incident ID, TargetResolutionTime, Priority, AffectedUser and Incident Classification as freebies :-)

11b) Click on the 'Assigned to User Notification Template and then on the right hand side, click Duplicate:

11c) Change the dropdown to select one of your custom MPs (I chose Antoni Custom MP)

11d) the template will be duplicated and saved as ‘Assigned To User Notification Template – Copy’ in the selected MP (It may take a moment for it to show up in the templates view, so refresh if needed.

11e) Double-click the ‘Assigned to User Notification Template – Copy’ and rename it. I renamed mine to ‘Antoni - Incident in Queue (Support Group)’

NOTE: The Targeted Class is Incident which is what we want in this case.

11f) In the message Subject, change Incident assigned to 'Incident in Queue'

11g) Take out the first two lines (from Dear to FirstName$) as we intend this notification template will go to a Distribution Group Email Address, rather than an individual

11h) Change 'The following incident has been assigned to you:' to ‘Incident placed in Queue’.

11i) Optionally, take out the Target Resolution Time string (from Target Resolution Time: $Context/Property[Type='CoreIncident!System.WorkItem.Incident']/TargetResolutionTime$) because chances are you won't use this functionality and will use the new SLA functionality instead as explained in Section 15 SLOs.

11j) Also, Optionally, change the Urgency from Medium to Low or High. It should look something like this

11k) Click Ok to save, and then Close once complete.

NOTE: If you include any HTML in the template, be sure to click the Send as HTML checkbox. In this case we are not using any HTML so we will leave it unchecked. Please see Optional 3 section of this blog post for details on creating more sophisticated notification templates with HTML.

12) Configure Subscriptions

In Service Manager, there are 3 places you can configure Subscriptions

Administration>Subscriptions>Recipient

Administration>Workflows> Select People To notify

Administration>Subscriptions>Related Recipient

A good rule of thumb to go by is that if you wish to use a hardcoded DL / individual email address then you will configure this under Administration>Subscriptions. .

If you need service manager to dynamically figure out and notify a stakeholder such as Affected User and / or Assigned to User, then you will probably want to use a workflow. When created in the Console, workflows can be created for the following classes:

Release Record

Desired Configuration Management

Service Request

Incident

Change Request

Activity

The Related recipient is an interesting one where occasionally you will find a scenario this is appropriate to use. One such example is SLAs when you wish to notify an assigned to user that an SLA is about to breach (enters the warning status). SLAs need to be created using the 'Service Level Instance Time Information' class which is why you cannot configure this in the workflows section of the UI (because workflows can only be created for the bullet list of classes shown above). Also in the case of SLAs, chances are you will want to notify a stakeholder (like the Assigned To User) that an SLA is about to breach in addition or instead of a hard-coded individual or team DL. Therefore within the subscription, you will specify 'Related recipients' rather than 'Recipient' This is an example of where the 'related recipients functionality can be used effectively.

One consideration of the Related recipients functionality is that the same template has to be used for the whole subscription, whereas in a workflow, you can specify one notification template for the affect User, a different notification template for the assigned to user etc. Not that bigger deal though as you can just create multiple subscriptions if necessary.

So here is an example for using each of these subscription methods:

Administration>Subscriptions>Recipient - Example: Notify a Support Group DL that an incident is in the queue

Administration>Workflows> Select People To notify - Example, when an incident is Assigned, Notify Created by User their incident was raised with an end user acknowledgement template and Notify the analyst it is assigned to, using the assigned to analyst template

Administration>Subscriptions>Related Recipient - Example: Notify Assigned To User that SLA has gone to warning status

Here is the detail on how to create each of these subscriptions:

Notify a Support Group DL that an Incident is in the queue

(Administration>Subscriptions>Recipient )

Note: it is required to have the channel set up prior to doing this which was configured in Section 4) Also, You will use the template that we created in the previous section or the one created in the Optional 3 section.

Note: The 'When an object is updated' criteria below will not catch brand new incidents, which is why we create this subscription twice - one for brand new incidents set to the 'helpdesk'; support group during creation. And then a second time using the 'when an object of the selected class is updated; option which catches existing incidents, or new incidents that are created and have an incident template applied which sets the support group.

Note that you have to associate a user / distribution group with the subscription, so ensure that the email address you will want to use for this notification is associated with a user / distribution group in AD, and that the AD connector has ran since the user / group was created in Service Manager and had the email address associated. You can search for it in the Configuration Items>users view which shows both users and groups.

12a) Navigate to Administration>Notifications>Subscriptions

12b) Click 'Create Subscription' and click Next in the Before You Begin' page, click Next

12c) In the General Page give the Subscription a descriptive name and optionally a subscription. I will call mine ‘Antoni - Notify HelpDesk of New Call in Q - Incident Created - Support Group = Helpdesk - HelpDesk DL’

TIP: In order to be as descriptive as possible with the name, you could put a placeholder in there, go through the rest of the create subscription wizard, and then come back to the General page and specify the name, once you know your criteria, template, and recipient which are good things to highlight in the name

12d) Configure the settings in the General Page as follows:

12e) Leave the default option selection in the dropdown of 'When an object of the selected class is created'

NOTE: You will create a second subscription (using the When an object of the Selected class is updated option) to catch existing incidents that get places in the helpdesk Queue either manually or via workflows applying a template that does this.

12f) Change the Targeted Class to Incident

12g) Change the Management Pack to one of your Custom MPs. I will use Antoni Custom MP.

TIP: Always check the MP listed before clicking Next. If a custom MP is listed prior to choosing the Incident class, the target MP to save it in will change to 'Service Manager Incident Management Configuration Library, so after selecting the class, be sure to select the appropriate custom MP

12h) In the Group / Queue selection click Next as we are narrowing down in the next 'Additional Criteria' page rather than this page. If you leave the default of no queues selected, then the subscription will apply to all Incidents (or instances of the class that you select)

12i) In the Available Properties <search> box start typing support group and then select it, click Add.
Ensure the Operator dropdown says 'Equals', and then in the value box, type Helpdesk (or the Support Group that you are creating the Subscription for)

12j) Choose a template such as the 'Antoni - Incident in Queue (Support Group)' template created in the previous exercise and click Next

12k) In the Recipient Dialog, either add a Distribution Group that corresponds to the people who work the selected Queue or, add the individual users. Verify that the correct email Address appears. If you do not see the user or distribution group that you know is associated with the email address you want to use, and you know this exists in AD / Exchange, then you may need to exit and synchronize the AD connector and then start creating the subscription again.

12l) In related Recipients click next.

TIP: You may like to add a related recipient here such as the assigned to user or affected user to acknowledge that the incident was placed in the Q. Remember however that if you do this, the same 'Antoni - Incident in Queue (support group)’' is the template that will be used to send all emails that are part of this particular subscription. For sending different templates to different users consider creating additional subscriptions or creating subscriptions in workflows as explained next.

12m) In Summary click Create, and once created, click Close

We will now repeat these steps with a couple of alterations, to create a subscription that fires when an existing (already created) incident is updated to the appropriate Queue.

12a) Navigate to Administration>Notifications>Subscriptions

12b) Click 'Create Subscription' and click Next in the Before You Begin' page, click Next

12c) In the General Page give the Subscription a descriptive name and optionally a subscription. I will call mine ‘Antoni - Notify HelpDesk of New Call in Q – Incident Updated - Support Group Changed to Helpdesk - HelpDesk DL’

12d) Configure the settings in the General Page as follows:

Change the dropdown of 'When an object of the selected class is created' to 'When an object of the Selected class is updated'

Change the Targeted Class to Incident

Change the Management Pack to one of your Custom MPs. I will use Antoni Custom MP.

12e) In the Group / Queue selection click Next as we are narrowing down in the next 'Additional Criteria' [page rather than this page. If you leave the default of no queues selected, then the subscription will apply to all Incidents (or instances of the class that you select

12f) within the 'Changed from' tab, In the Available Properties <search> box start typing support group and then select it, click Add.
Change the Equals dropdown to 'Does not Equal' and then in the value box, type Helpdesk (or the Support Group that you are creating the Subscription for).

12g) Click the 'Changed To' tab and In the Available Properties <search> box start typing support group and then select it, click Add.
leave the default of Equals in the dropdown to and then in the value box, type Helpdesk (or the Support Group that you are creating the Subscription for). Then Click next

NOTE: You will notice how after selecting the 'when an object of the selected class is updated' option in the first page, we have change from and changed to criteria, rather than just the 'criteria' tab

12h) Choose a template such as the 'Antoni - Incident in Queue (Support Group)' template created in the previous exercise and click Next

12i) In the Recipient Dialog, either add a Distribution Group that corresponds to the people who work the selected Queue or, add the individual users. Verify that the correct email Address appears. If you do not see the user or distribution group that you know is associated with the email address you want to use, and you know this exists in Ad / Exchange, then you may need to exit and synchronize the AD connector and then start creating the subscription again.

12j) In related Recipients click next.

TIP: You may like to add a related recipient here such as the assigned to user or affected user to acknowledge that the incident was placed in the Q. Remember however that if you do this, the same 'Antoni - Incident n Queue (support group)’ is the template that will be used to send all emails that are part of this particular subscription. For sending different templates to different users consider creating additional subscriptions or creating subscriptions in workflows as explained next.

12k) In Summary click Create, and once created, click Close

When an incident is Created by an Analyst in the console, Notify Created by User their incident was raised with an end user acknowledgement template and Notify the analyst it is assigned to, using the assigned to analyst template

(Administration>Workflows> Select People To notify)

12a) Go to Administration>Workflows>Configuration

12b) Double click 'Incident Event Workflow configuration

12c) In the 'Configure Workflows' dialog, click Add and click next in the 'Before You begin' dialog

12d) As with everything created, be as descriptive as possible for the name and description. If needed put a placeholder in and come back and modify it / add to it after you've gone through the other pages of the wizard, before you finalize and create it. I will call mine Antoni - Incident Created - Notify Created By and Affected User

In the check for events dropdown, leave 'when an object is created'.

NOTE: There is no class selection here because you are already in the workflows section purely for Incident related workflows.

12e) Change the MP to a custom MP. I chose Antoni Custom MP, Leave the 'Enabled' checkbox as True, and click Next

12f) In the Available Properties <search> box start typing source and then select it, click Add.
leave the default of Equals in the dropdown to and then in the value box, select Console. Then Click next

NOTE: In the Specify Event Criteria, you could leave this blank so it catches every incident created. In this scenario, I will change the 'Source' to Console, because this workflow is to cover the scenario where an end user calls the helpdesk, and an analyst raises the ticket, specifying the end user and the assigned to user.

NOTE: more likely they will assign to a support Group rather than an individual, leaving the 'assigned to user' blank and allowing someone from the Support group to see it in the Queue and assign it to themself. This is ok as the workflow will work either way at least notifying the end user, and additionally notifying the assigned to user if one is specified.

12g) In Select Incident Template, leave the default of 'Do not apply a template'. and Click Next

NOTE: We will use this feature in the next section, but for now just be aware that this is if you want to apply an incident template - it is nothing to do with the notification templates which will be selected din the next dialog.

12h) In Select People to notify page, Click the 'enable Notification' checkbox

12i) In User, Select Affected User. In Message template select 'End User Notification template' or a different template of your choice. then click Add

12j) Change the Affected User dropdown value to Assigned To User. Change Message Template from ‘End User Notification Template’ to ’Assigned to User Notification template' or a different template of your choice, then click Add.

It should look something like this:

12k) then Click Next, Create and Close.

Notify Assigned To User that SLA has gone to warning status

(Administration>Subscriptions>Related Recipient)

This is explained in Section 15 (SLAs). It basically involves creating a subscription that uses the Service Level Time Instance Class being updated, and the status field of that class changing from does not equals warning, to does equals warning. More details can be found in Section 15.

13) Configure Workflows (auto assign default incoming template)

Workflows can be designed in the Service Manager Console to do one (or both) of two actions:

Send Notifications - For instance you might have a workflow that fires when a new incident is created, and notifies the 'Created by User', 'Assigned to User' and 'Affected user' each using a different notification template. An example of this functionality was outlined in the previous section
Apply templates - for instance you might have a workflow that looks for incidents raised via the portal that have the word 'printer' in the title or description of the incident, and if found, the workflow will automatically assign the 'Printing Issue' incident template. This template could set important fields like the support group, priority and incident classification, which would set the incident up to match queue / view criteria.

This exercise is an example of creating a workflow that will do both of these things:

Workflow Scenario:

For Incidents that are raised from the portal that have the word print or printer in the title, the ‘Antoni Printing Issue Incident’ Template will be automatically applied. And in addition to this, the affected user will be notified using a template created for this purpose.

Start by creating both the incident template and notification template if you don't already have one you wish to use for this:

Printing Incident Template (Use section 8 if you need help) with the following or similar configuration:

Name = Antoni Printing Issue Incident Template

Support Group = Helpdesk

Incident Classification = Printing Problems

Urgency = Low
Impact = Low

Printing Incident Notification template (Use Section 11 if you need help) with the following or similar Configuration. I duplicated the existing 'end User Notification template' into my Antoni Custom MP and then specified the following:

Name = Antoni Printing Incident - End User
Subject - Changed 'An incident has been opened for you'. to 'A printing incident has been opened for you'.
Body - left as the default that was duplicated from the End User Notification template.

Create the workflow using the following steps:

13a) Go to Administration>Workflows>Configuration

13b) Double click 'Incident Event Workflow configuration'

13c) In the 'Configure Workflows' dialog, click Add and click next in the 'Before You begin' dialog

13d) As with everything created, be as descriptive as possible for the name and description. If needed put a placeholder in and come back and modify it / add to it after you've gone through the other pages of the wizard, before you finalize and create it.

I will call mine ‘Antoni - Printing Incident Created in Email or Portal - Apply Printing Incident template - Notify End User’

13e) In the check for events dropdown, leave 'when an object is created'.

NOTE: There is no class selection here because you are already in the workflows section purely for Incident related workflows.

13f) Change the MP to a custom MP. I chose Antoni Custom MP, Leave Enabled as True and Click Next

13g) In the Specify Event Criteria, configure this as shown below and click Next:

This narrows down this workflow to run, only if the user enters the words ‘print’ or ‘printer’ into the title /description fields on the portal, or if the user creates an incident via email with ‘print’ or ‘printer’ in the subject. The assumption here is that if an analyst is conducting telephone support and created a Printing incident in the Service Manager console, then they would apply the printing template manually, which is why we exclude incidents created in the console.

13h) In the Select Incident Template dialog, click 'Apply the following template' and choose the printing incident template you created for this exercise, and click next.

NOTE: After selecting the template, the dialog gives you a preview of the fields that the template will populate:

13i) In the Select People to notify click the "enable Notification' checkbox.

13j) Choose the Affected User and the Notification template created for this exercise. Then Click Add

13k) Click next, create and Close.

14) Notify on assignment / re-assignment

A key part of functionality I find most customers want is the ability to notify an 'Assigned to User' when an incident is assigned or re-assigned to them. I find the best way of doing this is using the xml which I shamelessly stole from my colleague Ketan's blog post here. I have copied the xml you will need for this below too.

On his blogpost, he explains the xml really well and how it functions. You can simply take this block of xml and save it as ServiceManager.IncidentAssignmentChanges.Notification.xml

NOTE: The ID Specified in the xml for the MP must match the filename of the MP

Once you have the xml file you can import it into Service Manager under Administration>Management Packs.

Before importing this xml, The one thing you definitely might like to consider changing is specifying your own notification template (otherwise the default 'Assigned to user Notification template' is used)

You can replace the Template GUID with your own template GUID, if you have one created by replacing this GUID in the xml (in between the Item Tags).

</WorkflowArrayParameter>

Here is a query you can use (run against the ServiceManager DB in SQL Management Studio) to find the GUID for your template (replace 'ant' with something that identifies the notification template you're after:

select
ObjectTemplateId, LTValue from ObjectTemplate ot
Inner join LocalizedText LT on LT.MPElementId = ot.ObjectTemplateId
where
ObjectTemplateTypeId='0814D9A7-8332-A5DF-2EC8-34D07F3D40DB'
and
ltvalue like '%ant%'

Here is the xml which you will need to save as ServiceManager.IncidentAssignmentChanges.Notification.xml and then import as a Management Pack into Service Manager:

<ManagementPack ContentReadable="true" SchemaVersion="1.1" OriginalSchemaVersion="1.1" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <Manifest> <Identity> <ID>ServiceManager.IncidentAssignmentChanges.Notification</ID> <Version>7.0.5244.0</Version> </Identity> <Name>Incident Assignment Changes Notification Workflow</Name> <References> <Reference Alias="WorkItem"> <ID>System.WorkItem.Library</ID> <Version>7.0.5244.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="Incident"> <ID>ServiceManager.IncidentManagement.Library</ID> <Version>7.0.5244.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="CoreIncident"> <ID>System.WorkItem.Incident.Library</ID> <Version>7.0.5244.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="SystemCenter"> <ID>Microsoft.SystemCenter.Library</ID> <Version>7.0.5244.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="SystemCenter1"> <ID>Microsoft.SystemCenter.Subscriptions</ID> <Version>7.0.5244.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="Administration"> <ID>Microsoft.EnterpriseManagement.ServiceManager.UI.Administration</ID> <Version>7.0.5244.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="System"> <ID>System.Library</ID> <Version>7.0.5244.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> </References> </Manifest> <Categories> <Category ID="IncidentConfigurationMPSolutionCategory" Value="Incident!Microsoft.EnterpriseManagement.ServiceManager.ManagementPack.Solution.IncidentManagement"> <ManagementPackName>ServiceManager.IncidentAssignmentChanges.Notification</ManagementPackName> <ManagementPackVersion>7.0.5244.0</ManagementPackVersion> </Category> <Category ID="Category.IncidentAssignmentChanges" Target="IncidentAssignmentChanges" Value="Administration!Microsoft.EnterpriseManagement.ServiceManager.Rules.WorkflowSubscriptions" /> </Categories> <Monitoring> <Rules> <Rule ID="IncidentAssignmentChanges" Enabled="true" Target="SystemCenter!Microsoft.SystemCenter.SubscriptionWorkflowTarget" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100"> <Category>Discovery</Category> <DataSources> <DataSource ID="DS" TypeID="SystemCenter1!Microsoft.SystemCenter.CmdbInstanceSubscription.DataSourceModule"> <Subscription> <RelationshipSubscription RelType="$MPElement[Name='WorkItem!System.WorkItemAssignedToUser']$" SourceType="$MPElement[Name='CoreIncident!System.WorkItem.Incident']$" TargetType="$MPElement[Name='System!System.Domain.User']$"> <AddRelationship> </AddRelationship> </RelationshipSubscription> <PollingIntervalInSeconds>10</PollingIntervalInSeconds> <BatchSize>100</BatchSize> </Subscription> </DataSource> </DataSources> <WriteActions> <WriteAction ID="WA" TypeID="SystemCenter1!Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskWriteAction"> <Subscription> <EnableBatchProcessing>true</EnableBatchProcessing> <WindowsWorkflowConfiguration> <AssemblyName>Microsoft.EnterpriseManagement.ServiceManager.Incident.Workflows</AssemblyName> <WorkflowTypeName>Microsoft.EnterpriseManagement.ServiceManager.Incident.Workflows.AutomaticIncidentChangeWorkflow</WorkflowTypeName> <WorkflowParameters> <WorkflowArrayParameter Name="InstanceIds" Type="guid"> <Item>$Data/BaseManagedEntityId$</Item> </WorkflowArrayParameter> <WorkflowParameter Name="NotificationRulesEnabled" Type="boolean">True</WorkflowParameter> <WorkflowArrayParameter Name="NotificationTemplates" Type="guid"> <Item>50dc32c2-6517-e9ea-dd99-0455383cab17</Item> </WorkflowArrayParameter> <WorkflowArrayParameter Name="UserAliasOrRelationships" Type="string"> <Item>15e577a3-6bf9-6713-4eac-ba5a5b7c4722</Item> </WorkflowArrayParameter> </WorkflowParameters> <RetryExceptions /> <RetryDelaySeconds>60</RetryDelaySeconds> <MaximumRunningTimeSeconds>1500</MaximumRunningTimeSeconds> </WindowsWorkflowConfiguration> </Subscription> </WriteAction> </WriteActions> </Rule> </Rules> </Monitoring> <LanguagePacks> <LanguagePack ID="ENU" IsDefault="true"> <DisplayStrings> <DisplayString ElementID="ServiceManager.IncidentAssignmentChanges.Notification"> <Name>Service Manager Incident Assignment Changes Notification Workflow</Name> <Description>Service Manager Incident Assignement Changes Workflow</Description> </DisplayString> <DisplayString ElementID="IncidentAssignmentChanges"> <Name>Incident Assignement Notification</Name> </DisplayString> </DisplayStrings> </LanguagePack> </LanguagePacks></ManagementPack> 

The same blog link has some other information and link to other blog posts that explain similar or extended functionality such as notifying an affected user / primary owner following assignment / re-assignment. The above xml code only takes care of the assigned to user, which is the main one most customers need.

15) Create Service Level Objectives

SLOs consist of 4 components:

Calendar

Metric

Queue

Thresholds (warning and Breach)

The calendar defines the time that the SLO clock is ticking. For instance, you create a calendar of 9-5 Monday - Friday and your SLO Breach threshold is an hour. If you create an incident at 6am in the morning, it will not breach until 10am, as the SLO clock only starts ticking at 9am.

The metric defines the duration that is being measured. for instance the duration between Created Time and Resolved time. Or another example would be Created Time to First Assigned Time.

The Queue defines the work items (incidents in this case) that the SLO applies to.

So for instance lets say the following is defined:

Calendar = 8am - 6pm Mon-Fri

Metric = Created Time to resolved Time
Queue = All Printing Incidents assigned to Tier 2 – helpdesk
Warning Threshold = 30 minutes
Breach Threshold = 1 hour

This is the resultant behavior:

SLO Scenario 1: A printing incident assigned to Tier 2 - helpdesk support Group is created at 6am in the morning and is resolved at 8.10 am in the morning. In this case neither the warning or Breach thresholds are exceeded, because the SLO clock was not ticking until 8am. So the incident only took 10 minutes of SLO time to get resolved.

SLO Scenario 2: A printing Incident assigned to tier 2 helpdesk Support group is created at 8am in the morning and is resolved at 11am in he morning. At 8.30 (warning threshold - 30 minutes before the target) the incident is in an SLO warning state. At 9am, it enters the SLO Breached state.

In this exercise, we will create the following 2 SLO objectives:

All Incidents should be Resolved within 5 days, warn after 4 days (1 Day prior to SLA Breached) using the 9-5mon-fri calendar
All Priority 1 Incidents Should be resolved within 4 hours, warn after 3 hours (1 hour prior to SLA breached) using the 9-5mon-fri calendar.

Start by creating your calendar. (Note multiple calendars can be created if desired)

15a) Click on Administration>Service Level Management>Calendar

15b) On the right hand side in the tasks pane, click 'Create Calendar

15c) Check the boxes for the days you want to apply and then enter the Start and End times in the boxes. If you enter a 24-hour time like 09:00 and hit tab, this will resolve to 09:00:00AM (17:00 for 5pm).

15d) Optionally add holidays. Click OK when you're done.

NOTE: The Related SLOs will be populated automatically later when you associate the calendar with the SLO.

It should look something like this when you're done:

TIP: you can pull holidays form outlook - take a look here for more:

Next, Configure the metrics you want:

NOTE: out the box you get two: One for Service Request Completion time, One for Incident Resolution time.

In this example, we will use the built-in Incident Resolution time metric, but optionally, you can create additional metrics using these steps:

Click on Service Level management>Metric

On the right hand side in the task pane, click Create Metric
Give the Metric a name such as Antoni - Incident Created to Incident First Assigned.
Next to class, hit Browse and choose Incident
In Start Date dropdown choose Created Date (although think of this as date and time)
In end Date choose First Assigned Date (also think of this as date and time) then Click OK.

Finally create your Service Level Objectives which brings the calendar, metric and queue together setting the SLO Warning and Breach thresholds. I will define 2 SLOs in this exercise

SLO 1: All Incidents should be Resolved within 5 days, warn after 4 days using the 9-5mon-fri calendar
SLO 2: All Priority 1 Incidents Should be resolved within 4 hours, warn after 3 hours using the 9-5mon-fri calendar.

SLO 1: All Incidents should be Resolved within 5 days, warn after 4 days using the 9-5mon-fri calendar

To define SLO 1 for all incidents:

15a) Click Administration>Service Level Management>Service Level Objectives

15b) on the right hand side, click Create Service Level Objective, and click next in the Before you begin dialog

15c) Give the SLO a name (good to include a reference to the Queue, metric, calendar and thresholds so again you may want to come back and set this after you have gone through the rest of the wizard. I will call mine ‘Antoni SLO - MF9-5cal - All Incidents - Resolution time - b5days w4days’. Believe me you will be pleased later on for being as descriptive as possible with your names :-)

15d) In Class click Browse and choose Incident

15e) Change the Management Pack to one of your custom MPs - I will use Antoni Custom MP.

15f) Leave the Enabled checkbox selected and click next

15g) choose the All Incidents Queue (Antoni - All Incidents in my case) and click Next

NOTE: Unlike some of the other Queue selection dialogs where not selecting a Q causes all instances of the class to apply, it is mandatory to pick a queue in this wizard which is why the Queues section of this guide had you create the All Incidents Queue.

15h) In Service Level Criteria, choose the Calendar, metric, Target and Warning thresholds. Mine looks like this:

NOTE: the warning threshold can sometimes get confusing. using the above example, I want the SLA to be breached after 5 business days but go into a warning after 4 days. So do I put 4 days (96 hours) or 1 day in here. The answer is 1 day as the warning threshold is the amount of time prior to an SLA Breach you want the incident to enter a 'SLA Warning' status for the purposes of emailing the assigned to user, or showing in a warning view etc.

15i) Click Next, Create and close

SLO 2: All Priority 1 Incidents Should be resolved within 4 hours, warn after 3 hours using the 9-5mon-fri calendar.

This SLO is set up using the same steps, as SLO 1, except for the Queue, I will choose my Antoni - All Priority 1 Incidents Queue and I will set 4 hours as my SLO Breach threshold, and 1 hour as my SLO Warning threshold.

16) Create User roles

If you're still with me, you have a pretty good well customized incident system set up so far! Let's keep going!

User Roles control what a user sees in the console. This is important both for security and ease of use.

You can either use the User Roles that are supplied out of the box, or create customized version of these. The ones out of the box cannot be customized other than adding associated individuals or groups to reach user role.

When Creating custom roles, this adds flexibility in being able to control access to the following elements:

Queues - for narrowing down work items that a user can see
Configuration Items - for narrowing down access to items such as computer and user CI records (requires creation of groups)
Catalog Item Groups - for narrowing down access to request and service offering in the portal (see my other blog posts on incident request offerings for more on this)
Tasks - for narrowing down the ability to use the tasks on the right-hand side
Views - for narrowing down the views that a user will see in the console
Form Templates - For narrowing down the form templates that can be applied to a work item
Classes (Author User Role only) - For narrowing down the classes that elements such as templates can be authored for.

TIP: The access is a combination of all of these which is particularly important for Queues and Views. for instance if you create a User Role called 'Infrastructure Team Incident Resolver, you may give access to the 'All Incidents' view that is supplied out of the box, and also narrow down the queues to just the 'All Infrastructure Team Incidents' Queue. When a user is associated with the 'Infrastructure Team Incident Resolver' User Role, and they look look at the 'All incidents' view in the console, they will actually only see Incidents that have 'Infrastructure Team' set as the support group (those that match the criteria specified for the 'All Infrastructure Team Incidents' Queue.)

Let's create this example User Role:

16a) Click on Administration>Security>User Roles

16b) Click the "Create User Role' task from the tasks pane on the right hand side and choose incident resolver in the flash out menu

16c) Enter a name such as Antoni Incident Resolver - Infrastructure Team and click Next

16d) In the Management Packs Page click Select All and then next

NOTE: as this page controls what you see in the following pages for selection, and I want to see everything available.

TIP: If you're doing a Incident Resolver User Role like this, you might choose to select all your custom MPs and all the internal MPs that have ' incident' in the title as this will make it easier when you're selecting views etc. in the following pages.

16e) In the Queues, click the 'Provide access to only the selected Queues' radio button and select the Queues (remember Queues are groups of work items) that you want to allow access too. In this case we will just choose Antoni - All Infrastructure team Incidents.

NOTE: This is relying on a person or workflow appropriately setting the support group to 'infrastructure Team' such that a member of the Infrastructure team will be able to see these incidents.

16f) Click Next in the Configuration item Groups page. To date, I personally have not seen anyone narrow down access to configuration groups, at least not in the initial configuration

16g) click next in the 'Catalog Item Groups'. This is to allow access to certain request offerings and service offerings which again is something usually not required at these early stages of configuration.

16h) In Tasks, you can narrow down the tasks that users have access to. In this example I will leave all tasks selected and click next

16i) In Views, choose the views that you would like to give access to, and click Next.

TIP: Combining Queues and Views as discussed earlier can help prevent the need to create custom views as you are customizing the built-in Views in effect, by narrowing down the Queues in the User roles.

TIP: One thing I will often do in the 'Views' page (in particular when I'm creating an Incident Resolver use role) is sort by the 'Management Packs' column and scroll down to the 'Service Manager Incident Management Configuration Library' Views as these are the views I will often want to include in my incident resolver view. A good starting point would be:

All Incidents

My Incidents

All Open Unassigned Incidents

Incident with SLA Warning

Incident with SLA Breach

TIP: Don't forget your Configuration Item views which can be found under the 'Service Manager Configuration management Configuration Library' and 'Service Manager Configuration management Library' Management packs.

You may want to give access to All Windows Computers, Users etc..

16j) In the form Templates page, either narrow down access to certain forms, or leave the default of 'All forms can be accessed' I will leave the default in this case.

16k) In Users, click Add and select the AD Users or Groups that you want to associate with the Custom User Role. I will select a custom AD group I created for this purpose called Incident Resolvers.

16l) Click Next, then Create and then Close.

NOTE: User Roles are cumulative so as you get added to additional user roles (either individually or via associated AD group membership), the user will receive cumulative permissions.

TIP: You can find a matrix of permissions associated with each user role here

TIP: You can launch a second console simultaneously as a test user associated with a user ole, to test the effects of creating a user role. Shift and right-click over the Service Manager console will give you the options to launch as a different user.

17) Incident from Email

This is the email functionality that is offered out of the box and allows a user to send an email to a given email address. Exchange will forward emails sent to this address to an SMTP server that Service Manager is watching. For all emails that Service Manager finds in the drop box, it will convert these into incidents using the subject as the title, and the body as the message.

Details on how to set this up can be found here. (Note steps are written for Exchange 2010 but the steps are mostly the same for 2012 with some slight terminology changes)

For more enhanced email functionality, consider the Exchange connector which you can find details of here:

Please be aware that the Exchange Connector is currently not supported by Microsoft.

18) Incident Portal Configuration (change perms in SharePoint and SCSM if required)

The Self-service portal is designed with end users in mind as a place where they can go ands raise new incidents / service requests, check knowledge articles / announcements, and check the status of their current incidents and service requests.

It is not designed as a place for analysts and technicians to update work items.

In addition to this, any users that have review activities assigned to them (reviewers) can go in and approve or reject from the portal, and activity implementers can also mark activates assigned to them as completed.

The My in 'my requests' refers to the user being set as the 'Affected User' - not the Created by or assigned to user. So even if an incident is Assigned to you (you are the Assigned to user) you would only see the incident in the portal if you were also designated as the 'Affected User'

When updating incidents, Analysts or technicians make updates in the 'Action Log' area of the incident. If they mark a comment as Private, this prevents it from being displayed in the self-service portal to the end user (affected user) checking status and progress on their incident.

This assumes that you set up the self-service portal in SharePoint already and can access the site.

The URL should be something like:

http://[SharePointServer]:[PortNumber]/SMPortal/

The NT AUTHORITY\Authenticated Users Group is in the 'End User' User Role which grants end users access to the portal from the Service Manager perspective, so the only permissions that need to be allocated are through SharePoint which can be done in the following way:

a) In the upper left area of the web page, click Site Actions, and then click Site Permissions.

b) On the SharePoint ribbon, click Grant Permissions.

c) In the Grant Permissions box, in the Users/Groups box, type the Active Directory name for the users or user groups to whom you want to grant access.

d) In the Grant Permissions area, click Read – Can view pages and list items and download documents, and then click OK.

e) Close the browser.
Reference: http://technet.microsoft.com/en-us/library/hh495661.aspx

19) Knowledge Base Integration

You may also want to create Knowledge Articles and associate these to some of your templates or request Offerings.

The key thing to note is that an article has to be set to Published, in order for a Knowledge Article to appear out in the portal:

20) Announcements

You will see in the console (Administration) an Announcements node.

This was included with the intention of being able to publish announcements on the Self Service portal home page.

This functionality currently requires additional customization outside of the Service Manager console and details on how to achieve this with Orchestrator can be found here.

NOW WHAT?!

So that's the end of all the initial configuration I suggest. The nice thing is that if you have gone through all this is that many of the same principles, tips and processes of customizing used here apply to other areas of Service Manager

The same concepts discussed above like templates, workflows, notification templates, work items, config items etc. can all be configured in a similar fashion for other classes such as Service requests, just by substituting the incident class for the service request class.

OPTIONAL 1) Create your own Incident Request Offering allowing customization of incident form

(e.g. remove classification, impact and urgency fields so these are only set by an analyst / technician rather than the end user)

a) Firstly, create an incident template that sets all the required default values. I created one like this:

b) Create a Service Offering that you want the Request Offering to be classified under. In my case I will use the a Service Offering called Incidents which comes under my Helpdesk Catalog.

(Details of how to of this can be found in steps 1-3 on this post: http://blogs.technet.com/b/antoni/archive/2012/06/06/how-to-raise-an-incident-on-behalf-of-a-different-user.aspx )

c) Create a request Offering using the following steps:

d) Navigate to Library>Service Catalog>Request Offerings>All Request Offerings and in the tasks pane, click Create Request Offering

e) Click Next in the 'Before you Begin Page

f) In General, give the Request Offering a name (I called mine Incident (Basic)') and then select your custom incident template that has the default set. In my case I will choose the 'Antoni basic Incident' template

NOTE If you just click the main 'Select Template' button only SR Templates will be shown. to show Incident templates you need to click the arrow to the right of the button and select Incident.

g) Configure prompts for the fields you would like the user to enter (in my case title, description and file attachment). In my case note that I made the File Attachment input optional.

h) Click Next and In the configure prompts page, click on each prompt and configure and desired input mask / character limit etc., then click Next:

i) In the map prompts page you will map the user input to fields in the incident. We will map the brief description to the 'Title' field of the incident and the Details description to the descripting field of the incident. Ensure Incident is selected and click the dropdown next to Title, choose your first prompt. click the dropdown in the prompt output in the Description row,, and choose the second prompt. It should look like this:

j) Click Next in the Map Prompts Page and then next in the Knowledge Articles page

TIP: If you add Knowledge articles here, they will display in the portal before the user creates an incident using this request offering

j) In the Publish page, change the Offering Status to Published and then click next. Then click Create, and then Close.

NOTE: You need to ensure the Service Offering and Request Offering both appear in this 'Published' status in order to see this on the portal. A published service offering will only show up, once a request offering has been created as part of the service offering.

k) navigate to Service catalog,>All Service Offerings. Double click the Service offering that you want to add the request offering too (I will use incidents)

l) click the Request Offering page, and then click the Add button. Add the Request Offering (Incident (Basic)) in my case, click add then ok. then Click OK in the Edit Service Offering Dialog

OPTIONAL 2 ) Create Request Offering to allow users to raise incidents on behalf of other user

Steps on how to do this can be found here - http://blogs.technet.com/b/antoni/archive/2012/06/06/how-to-raise-an-incident-on-behalf-of-a-different-user.aspx

OPTIONAL 3) Enhance your Email notifications sent out by Service Manager

a) Start in Microsoft Word and create the Table that you would like to appear

I will normally use one of these:

TIP: You could use different color for different templates. For instance you might have a notification template notifying helpdesk of priority 1 incidents that has a red table and then a notification template notifying helpdesk of priority 2 incidents that has a different coloured table.

b) Set up the table with the labels and where the actual values will appear put a placeholder like this:

This will come into play later when you're filtering through the HTML to figure out where you want to place the variable, and will make this a lot easier :-) C)

c) And then here is the magic part. Click File, Save As and save the doc as a webpage.

d) Open up in Notepad and there is all your html.

e) Search for <table class= and copy from <table class=down to </table>

f) In service Manager, navigate to Administration>Notifications>Templates and Either Create a new template, or duplicate an existing one. In this case I will duplicate the 'Assigned to User Notification Template'

NOTE: Be sure to pick the Assigned To User Notification template from the Service Manager INCIDENT Management MP and not the Service Manager SERVICE MP. Otherwise your template will be associated with the Service Request class rather than the incident class.

g) Pick a Custom MP to duplicate into (I chose Antoni Custom MP)

h) The template will be created as Assigned To User Notification Template - Copy so double-click it and rename it.

I called mine Antoni VN - Incident in Queue (Support Group) where VN stands for Visually Nice :-) (hey, I'm writing this on a Friday :-)

i) Click on the template Design Page or scroll down to it (it al takes you to the same place :-) and then paste in the table you copied into the template. I pasted mine right at the bottom.

j) Scroll down to the first placeholder:

k) Delete the placeholder you inserted and Replace it with the variable(s) that t you want to insert. Do this by clicking the Insert button, typing in the variable you want in the available properties box, select the field, and the click the Add button

In my case, I will add the ID and Title so it looks like this when I'm done:

l) Repeat this for the other placeholders that you included, replacing the placeholder with the variable using the Insert button.

NOTE: for the affected User and other relationships you can scroll down on the left hand side underneath incident:

m) if desired, add text above and below the table and also configure your subject as you would like it to be appear.

I ended up with the following

Message Subject:

Incident in Queue: $Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Id$ - $Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Title$

Message Body:

INCIDENT IN QUEUE:

< table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
< tr>
<td width=233 valign=top style='width:175.1pt;border:solid #7BA0CD 1.0pt;
background:#D3DFEE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
Incident
ID and Title
</td>
<td width=405 valign=top style='width:303.7pt;border:solid #7BA0CD 1.0pt;
border-left:none;background:#D3DFEE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Id$ - $Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Title$
</td>
< /tr>
< tr>
<td width=233 valign=top style='width:175.1pt;border:solid #7BA0CD 1.0pt;
border-top:none;background:#A7BFDE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
Priority
</td>
<td width=405 valign=top style='width:303.7pt;border-top:none;border-left:
none;border-bottom:solid #7BA0CD 1.0pt;border-right:solid #7BA0CD 1.0pt;
background:#A7BFDE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem.TroubleTicket']/Priority$
</td>
< /tr>
< tr>
<td width=233 valign=top style='width:175.1pt;border:solid #7BA0CD 1.0pt;
border-top:none;background:#D3DFEE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
Affected
User
</td>
<td width=405 valign=top style='width:303.7pt;border-top:none;border-left:
none;border-bottom:solid #7BA0CD 1.0pt;border-right:solid #7BA0CD 1.0pt;
background:#D3DFEE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
$Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItemAffectedUser' TypeConstraint='CustomSystem_Library!System.User']$?$DisplayName$?
</td>
< /tr>
< tr>
<td width=233 valign=top style='width:175.1pt;border:solid #7BA0CD 1.0pt;
border-top:none;background:#A7BFDE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
Classification
Category
</td>
<td width=405 valign=top style='width:303.7pt;border-top:none;border-left:
none;border-bottom:solid #7BA0CD 1.0pt;border-right:solid #7BA0CD 1.0pt;
background:#A7BFDE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Classification$
</td>
< /tr>
< tr style='height:3.0pt'>
<td width=233 valign=top style='width:175.1pt;border:solid #7BA0CD 1.0pt;
border-top:none;background:#D3DFEE;padding:5.75pt 5.75pt 5.75pt 5.75pt;
height:3.0pt'>
Support
Group
</td>
<td width=405 valign=top style='width:303.7pt;border-top:none;border-left:
none;border-bottom:solid #7BA0CD 1.0pt;border-right:solid #7BA0CD 1.0pt;
background:#D3DFEE;padding:5.75pt 5.75pt 5.75pt 5.75pt;height:3.0pt'>
$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/TierQueue$
</td>
< /tr>
< tr>
<td width=233 valign=top style='width:175.1pt;border:solid #7BA0CD 1.0pt;
border-top:none;background:#A7BFDE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
Source
</td>
<td width=405 valign=top style='width:303.7pt;border-top:none;border-left:
none;border-bottom:solid #7BA0CD 1.0pt;border-right:solid #7BA0CD 1.0pt;
background:#A7BFDE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Source$
</td>
< /tr>
< tr>
<td width=233 valign=top style='width:175.1pt;border:solid #7BA0CD 1.0pt;
border-top:none;background:#D3DFEE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
Created
Date
</td>
<td width=405 valign=top style='width:303.7pt;border-top:none;border-left:
none;border-bottom:solid #7BA0CD 1.0pt;border-right:solid #7BA0CD 1.0pt;
background:#D3DFEE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/CreatedDate$
</td>
< /tr>
< tr>
<td width=233 valign=top style='width:175.1pt;border:solid #7BA0CD 1.0pt;
border-top:none;background:#A7BFDE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
Status
</td>
<td width=405 valign=top style='width:303.7pt;border-top:none;border-left:
none;border-bottom:solid #7BA0CD 1.0pt;border-right:solid #7BA0CD 1.0pt;
background:#A7BFDE;padding:5.75pt 5.75pt 5.75pt 5.75pt'>
$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Status$
</td>
< /tr>
< /table>

This is an automated
email from System Center 2012 – Service Manager

NOTE: BE SURE TO CLICK THE SEND AS HTML box :-)

n) Click OK

o) If you followed section 12, you can navigate to Channels>Subscriptions. Double click the Subscription created which notifies the support group of a new call in their Q, Click on the template page and then select the notifiation template that we just created, then click OK.

p) Create a new incident and specify the support group

This is how the result looks:

System Center 2012 Suite Integration blog Posts on the way :-)

2012-06-07T14:29:00Z

Recently, I have been working a lot on integration scenarios with System Center 2012 Service Manager, Orchestrator and Operations Manager. I figured it would be good to blog about some of these. I plan on posting more blogs as time permits, demonstrating some of these scenarios and how they can be achieved.