SCOM 2012 R2 Update Rollup 2 Released

Update Rollup 2 for System Center 2012 R2 Operations Manager


The UR2 has been released and it will be fixing the Dashboards and Widgets issues.

Issues that are fixed in this update rollup

Operations Manager

Issue 1

This update rollup makes the stored procedure performance aggregate more robust against out-of-range values.

Issue 2

Adding multiple regular expressions (RegEx) to a group definition causes an SQL exception when the group is added or run.

Issue 3

Web applications fail when they are monitored by the System Center Operations Manager 2012 R2 APM agent.

Issue 4

Service Level Objectives (SLO) dashboards sometimes load in several seconds and sometimes take minutes to load. Additionally, the dashboard is empty after it loads in some cases.

Issue 5

Operations Manager Console crashes when you try to override the scope in the Authoring pane.

Issue 6

The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.

Issue 7

This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 1.

Issue 8

SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse workflows.

Issue 9

This update rollup includes a fix for the Event Data source.

Operations Manager - UNIX and Linux Monitoring (Management Pack Update)

Issue 1

All IBM WebSphere application servers that run on Linux or AIX computers are not automatically discovered by the Management Pack for Java Enterprise Edition (JEE) if multiple application servers are defined in a single WebSphere profile.






How to install the UR2 on SCOM 2012 R2?

Supported installation order

We recommend that you install this update rollup package by following these steps in the given order:

1. Install the update rollup package on the following server infrastructure:
   • Management server or servers
   • Gateway servers
   • Web console server role computers
   • Operations console role computers
2. Apply SQL scripts (see installation information).
3. Manually import the management packs.

Notes

• If the Connected MG/Tiering feature is enabled, you should first update the top tier of the Connected MG/Tiering feature.
• Update Rollup 2 files have a version number of 10226.1011.

Installation instructions

To download the update rollup package and extract the files that are contained in this update rollup package, follow these steps:

1. Download the update packages that Microsoft Update provides for each computer. Microsoft Update provides the appropriate updates according to the components that are installed on each computer.
2. Apply the appropriate MSP files on each computer.
   
   Note MSP files are included in the update rollup package. Apply all MSP files that relate to a specific computer. For example, if the web console and console roles are installed on a management server, apply the MSP files on the management server. Apply one MSP file on a server for each specific role that the server holds.
3. Run the following SQL script on the Database Server against the OperationsManagerDB database:
   
   
   
   

   update_rollup_mom_db.sql

   
   Note The path to the script is:
   
   
   %SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server \SQL Script for Update Rollups\
4. Import the following management packs:
   • Microsoft.SystemCenter.Advisor.mpb
   • Microsoft.SystemCenter.Advisor.Internal.mpb
   • Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependency:
     • Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the SCOM 2012 R2 RTM media
   • Microsoft.SystemCenter.Visualization.Library.mpb
   
   
   

More details:
http://support.microsoft.com/kb/2929891