This article describes the issues that are fixed in Update Rollup 2 for Microsoft System Center 2012 R2 Operations Manager and the Linux and Unix Monitoring Pack. Additionally, this article contains the installation instructions for Update Rollup 2 for System Center 2012 R2 Operations Manager.
This update rollup makes the stored procedure performance aggregate more robust against out-of-range values.
Adding multiple regular expressions (RegEx) to a group definition causes an SQL exception when the group is added or run.
Web applications fail when they are monitored by the System Center Operations Manager 2012 R2 APM agent.
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.
Operations Manager Console crashes when you try to override the scope in the Authoring pane.
The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.
This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 1.
SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse workflows.
This update rollup includes a fix for the Event Data source.
Operations Manager - UNIX and Linux Monitoring (Management Pack Update)
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.
After you install this update rollup package on all roles on the server that is running System Center Operations Manager 2012 R2 (except on the Gateway role), the updates do not appear in the Add or Remove Programs item in Control Panel.
After you install this update rollup package, the version number of the console is not changed.
After you install this update rollup package on a web console, you receive the following error message in Internet Explorer:
Server Error in '/OperationsManager' Application.
To resolve this issue, close and then restart Internet Explorer.
Agent is not updated when you use Pending Patch view in the Operations Manager console.
To work around this issue, deploy the update to agents by using the Repair option. To do this, expand Device Management in the Administration hierarchy, right-click Agent Managed, and then click Repair to repair the agents.
Agent is not updated when you install from the gateway computer.
To work around this issue, copy the agent update from the SCOM server to the gateway computer.
For example, copy KB2929891-amd64-Agent.msp from the following:
\\SCOM Server\Program Files\System Center Operations Manager\Gateway\AgentManagement\amd64
Then, copy KB2929891-amd64-Agent.msp to the following:
\\SCOM Gateway\Program Files\System Center Operations Manager\Gateway\AgentManagement\amd64
Deploy the update to agents by using the Repair option. To do this, expand Device Management in the Administration hierarchy, right-click Agent Managed, and then click Repair to repair the agents.
When you try to import Microsoft.SystemCenter.Visualization.Component.Library, the import fails because of missing dependencies.
To resolve this issue, import Microsoft.SystemCenter.Visualization.Component.Library again.
This update rollup package is available from Microsoft Update in the following languages:
Chinese Simplified (CHS)
Portuguese (Brazil) (PTB)
Chinese Traditional (CHT)
Portuguese (Portugal) (PTG)
Chinese Hong Kong (HK)
Some components are language neutral, and the updates for these components are not localized.
You must run this update rollup as an administrator.
If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.
To start a new instance of Microsoft Silverlight, clear the browser cache in Silverlight, and then restart Silverlight.
Do not install this update rollup package immediately after you install the System Center 2012 R2 server. Otherwise, the Health Service state may not be initialized.
If User Account Control is enabled, run the .msp update files from an elevated command prompt.
You must have System Administrator rights on the database instances for the Operational Database and Data warehouse to apply updates to these databases.
To enable the web console fixes, add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:
You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
The fix for the data warehouse BULK insert commands timeout issue described in Update Rollup 1
for System Center 2012 R2 Operations Manager adds a registry key that can be used to set the time-out value (in seconds) for the data warehouse BULK insert commands. These are the commands that insert new data into the data warehouse.
Note This key must be manually added on any management server on which you wish to override the default bulk insert command timeout.
Note Set this value in seconds. For example, for a 40 second time-out, set this value to 40.
Supported installation order
We recommend that you install this update rollup package by following these steps in the given order:
Install the update rollup package on the following server infrastructure:
Management server or servers
Web console server role computers
Operations console role computers
Apply SQL scripts (see installation information).
Manually import the management packs.
Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.
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.1015.
To download the update rollup package and extract the files that are contained in this update rollup package, follow these steps:
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.
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.
Run the following SQL script on the Database Server against the OperationsManagerDB database:
Note The path to the script is:
%SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server \SQL Script for Update Rollups\
Run the following SQL script on the Database Server against the OperationsManagerDWdatabase:
Import the following management packs:
Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependency:
Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the SCOM 2012 R2 RTM media