New and great book from Kerrie Meyler, Kurt Van Hoecke, Samuel Erskine and Steve Buchanan about SCSM 2012, the “System Center 2012 Service Manager Unleashed” is released! Must Have book for all who interested about SCSM 2012 and want to learn more!
In last two articles of SLA series I was wrote about storing of the SLA objects and describe how it’s works.Today it’s time to talk about some “hidden” features of the SLA management system in SCSM 2012. Most of this features are available out-of-box and supported by Microsoft but some of them are not.
In Part 1 of this series I described objects model required for SLA management system in SCSM 2012. Now it’s time to figured out how all this things works.
SLA management system in SCSM 2012 is one of the most powerful feature in contrast with SCSM 2010 where we can use only 24/7 SLA. But in this cycle of articles I don’t want to show you to setup SLA management in click-click-next guide. My goal is to show you how SLA management settings are stored, handled and worked. I hope what this will allow you to use all feature of the SLA management system in SCSM 2012.
This is not a technical article but some kind of news. With SLA feature you can create a “rule” how to apply SLA to SCSM’s objects like incidents or service request (or any other object). If you don’t know how to do that please welcome to Rodney’s blogposts series: Part 1, Part 2 and Part 3.
But many peoples ask the one question: can we pause SLA depend from status or anything else? For example, how to stop SLA timer if status of incident changed to Pending? Before this week all who answer on this question (me too) ask “No, it’s possible”. But in fact you can (but see the note and the end of this article).
First feature of the AVE 2.0 Pro version: Auto-Refresh.
When you create your own classes, views or folders sometime you need link existing images to them. To do that you must know ID or Name of the image. But all images located in several management pack so find them is not a easiest work. Near I provide full list of images available in SCSM 2012. This table contains image itself, size, id and name grouped by management pack.
Very short blogpost. SCOM agent of any version DOESN’T work on SCSM 2012 servers, even don’t try to install it, you can damage your SCSM installation. This is true for Beta, and, unfortunately, this is true for RTM too. So the only way to monitor SCSM servers with SCOM is a using agentless monitoring.
This is WRONG and confirmed by product team. OpsMgr agent of any versions still CAN’T coexist with SCSM 2012 RTM.
Updated 22.07.2013. Information about SCSM 2012 SP1. The SCSM 201 SP1 already contains the SCOM 2012 SP1 agent. For you this means:
- You can attach SCSM 2012 SP1 server to SCOM 2012 SP1 as manually installed. You no need to install agent on SCSM 2012 SP1 Server.
- You CAN’T update the SCSM 2012 SP1 agent to any new version of the SCOM 2012 Sp1 agent. Please don’t try to install SCOM agent’ UR on SCSM 2012 SP1 Server..
Unfortunately, AD connect doesn’t have a ability to change it schedule. For SCSM 2010 AD connector runs one per hour, for SCSM 2012 it run once per 24 hours. For small domain this is acceptable schedule but for large domains with many users it can be potential risk of overload of the SQL or SCSM servers. AD connector get from AD only objects changes since last run but even this amount of data can be large and reduce workload to SCSM management server and even more to SQL server.
Office365 is a cloud-based solution which allows you to host email and SharePoint at microsoft’s servers on the cloud. And if you already use this solution and starting using the SCSM when early or later you want to send notifications to Exchange Online mailboxes. That simple at first glance solution is not really simple. The main problem that Office365 doesn’t support Windows authentication. So the only way is send all emails through your local SMTP relay. In this post I’ll talk how to setup and configure all chain to send notifications from SCSM to Office365.