System Center 2012 Self-Study Guide - Orchestrator and Service Manager

System Center 2012 Self-Study Guide - Orchestrator and Service Manager

  • Comments 2
  • Likes

NewDocsIntoHeadAre you looking for a good way to get started learning everything that’s new in Orchestrator 2012 and SCSM? If so then here’s the guide for you:

=====

In this post, we're turning to two more components of System Center 2012, Orchestrator and Service Manager. For those of you who need a brief summary of these System Center components, I've provided brief definitions below:

Orchestrator - "Orchestrator is a workflow management solution for the data center. Orchestrator lets you automate the creation, monitoring, and deployment of resources in your environment."

Service Manager - "Service Manager provides an integrated platform for automating and adapting your organization’s IT service management best practices, such as those found in Microsoft Operations Framework (MOF) and Information Technology Infrastructure Library (ITIL). It provides built-in processes for incident and problem resolution, change control, and asset lifecycle management."

=====

For the complete Orchestrator and SCSM self study guide please see the following:

System Center 2012 Self-Study Guide (Part 6 - Orchestrator and Service Manager)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity- support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • <p>Hi JC</p> <p>I have a couple of quick questions if I may. I am relatively new to Service Manager and Orchestrator. I am trying to do a couple of things with them:</p> <p>1) I want to monitor disk space on servers. If the disk space goes over a certain threshold, I want to delete certain files, and log an incident in service manager and mark that as resolved.</p> <p>2) I want to monitor some services on servers, if the service stops, to automatically start the service and similarly log a ticket in service manager and mark that as resolved.</p> <p>I have Operations Manager installed and I can use Operations Manager to leverage the monitoring side of things. Can this be done? If so, can you please point me towards the direction of how to. I would really appreciate any assistance. Please help :(</p> <p>Regards,</p> <p>Dipan</p>

  • <p>@Dipsg</p> <p>Set up the SCOM alert - &gt; SCSM incident connector.</p> <p>Disk space monitoring comes out of the box in SCOM but you might want to configure it slightly differently depending on your requirements.</p> <p>You&#39;ll need to use the &#39;Add Monitoring&#39; wizard to create a monitor for the Windows Service(s) that you want to monitor.</p> <p>Once you have that done the monitoring will generate alerts which will be converted into incidents in SCSM automatically.</p> <p>Then set up a SCO runbook to monitor for the creation of those types of incidents in SCSM. &nbsp;Have the runbook traverse the relationship from the incident to the computer that the incident is about. &nbsp;Use that information to restart the service on the computer or delete files on the computer. &nbsp;The act of starting the service or deleting the files will cause the monitors in SCOM to go back to a green state. &nbsp;Then the alert will be automatically resolved in SCOM which will cause the incident in SCSM to automatically be resolved.</p>