Service Manager 2012 R2 Preview – Features and updates

Just installed Service Manager 2012 R2 Preview version!

Download available here:

As I couldn’t find any good release notes information, I thought I’d make a first-move on any new stuff.  I will try to update this post regularly as I discover things.

These are the official release notes:

What’s new in Service Manager 2012 R2: 

Release notes for Service Manager 2012 R2:

The links sound promising, but doesn’t actually state anything.


I installed this on a virtual machine running Windows Server 2012 R2 Preview Standard edition with SQL2012(yeah why not go all in on R2? Smile). Not much to say here. It’s basically the same install procedure as SCSM2012 version, didn’t encounter any issues and the prerequisites are the same.

MSI (s) (E8:3C) [12:23:30:295]: Product: Microsoft System Center 2012 R2 Service Manager — Installation completed successfully.

MSI (s) (E8:3C) [12:23:30:297]: Windows Installer installed the product. Product Name: Microsoft System Center 2012 R2 Service Manager. Product Version: 7.5.3046.0. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 0.


Lets get started.

First thing I noticed was a new console logo design when starting up the console:



From here it pretty much looks the same. I went ahead to check different things, but quickly realized this would be to find a needle in a haystack. So I checked the Management Packs to see any difference. No new Management Packs added. Anything changed in the MP’s then? To figure that out I tried to do some comparison with the file sizes from SCSM2012SP1 with CU2 and the preview version:


This indicated 4 Management packs differences:

However, a powershell comparison of the content revealed that only one management pack had any real difference. The other Management Packs had my own custom changes: ex. I had an AD-Connector and had added a test Support Group.

So the only change to be found besides new version numbers in the management packs was this:


New code added:

<xsd:element name="TfsWorkItemId" type="xsd:string" minOccurs="0">
                    <xsd:documentation>with specific TFS work item id</xsd:documentation>
                <xsd:element name="TfsWorkItemOwner" type="xsd:string" minOccurs="0">
                    <xsd:documentation>with specific TFS work item owner</xsd:documentation>

This is a subsection of the ViewType: Microsoft.SystemCenter.AlertViewType

So likely a Team Foundation Server extension to the SCOM agent. from:

"In System Center 2012 R2 Operations Manager, you can synchronize Operations Manager alerts and Team Foundation Server (TFS) work items. When synchronization is enabled, IT operations can then assign alerts to the engineering team. Assigning an alert to engineering creates a new work item in TFS. The workflow will track and synchronize any changes that are made to TFS work items and any associated Operations Manager alerts."

So nothing big yet, though I haven’t checked the dll files or the web portal, but if this is the only change in the Management Packs it could look slim with the rest. We’ll see…

Files changes

A comparison of the Service Manager folder revealed some new folders and files. A Microsoft.IntelliTrace.Profiler.12.0.0.SCui.dll has been added to several folders and an Advisor folder is added as well. Normally Intellitrace is used as debugging in Visual Studio to record details about previous events and actions. This is something already available for Operations Manager, but seems to be enabled in Service Manager now so we’ll have a more granular debugging when error occurs. Read more here how it works: and here:


"System Center Advisor is an online service that analyzes installations of Microsoft server software. With the latest preview version of Advisor and Update Rollup 2 of System Center 2012 Service Pack 1 (SP1), you can now view Advisor alerts in the Operations Manager Operations console."

That’s it for now. The content in the dll files might have added content, but I wasn’t able to make sense of the comparison here, and couldn’t find any descent decompiling comparison tool.

Next up is installing the web portal – on a Sharepoint 2013!

Unfortunately this didn’t work, it’s still the same prerequisite failure:


I don’t know if this is just due to the wizard setup not being updated or it actually isn’t supported. To check this we’d have to install it via the msi file with all the right parameters, not something I’m going to do just now.


Changes found:

1) A new console logo

2) Support for Operations Manager New Alert Fields of TFS Work Item ID and TFS Work Item Owner

3) Support for System Center Advisor (what that actually implies is a little unclear at the moment).

This is of course only a preview version so we could see more changes to come and I  might have missed something in the comparison too, but for now a diplomatic conclusion must be that if you’re waiting for R2 to be released before start using Service Manager, there is no need to wait Smile.

By |2013-06-25T16:42:48+00:00June 25th, 2013|Service Manager (SCSM)|1 Comment

About the Author:

Morten Meisler
Consultant / Developer / Trainer Key areas / products: System Center Service Manager System Center Operations Manager Automation (System Center Orchestrator / Service Management Automation (SMA)) Development: C#.Net, Powershell, SQL, Web development / HTML5 (Javascript,jQuery,CSS,HTML, Wordpress etc.)

One Comment

  1. APJ June 26, 2013 at 20:16 - Reply

    SM feels like an annexed product. There’s nothing new, nothing to address the myriad complexities, the “new” portal does not actually exist. I predict that MS will abandon this as an on-perm solution entirely. A real shame as it did show real promise, but they built it on the wrong framework from day one.

    How the company that brought us SharePoint could use SharePoint pointlessly for the portal and then not for the knowledgebase is baffling. The product should have been built on CRM duh!it is now an over-complex mess that MS can’t dig themselves out of.

Leave A Comment