Description of Update Rollup 2 for System Center 2012 R2 Operations Manager

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.

Microsoft Update

To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an applicable System Center 2012 R2 component installed:

1. Click Start, and then click Control Panel.

2. In Control Panel, double-click Windows Update.

3. In the Windows Update window, click Check Online for updates from Microsoft Update.

4. Click Important updates are available.

5. Select the Update Rollup 2 package, and then click OK.

6. To install the update package, click Install updates.

Known issues for this update rollup

• 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.

Installation notes

• This update rollup package is available from Microsoft Update in the following languages:

  • Chinese Simplified (CHS)

  • Japanese (JPN)

  • French (FRA)

  • German (DEU)

  • Russian (RUS)

  • Italian (ITA)

  • Spanish (ESN)

  • Portuguese (Brazil) (PTB)

  • Chinese Traditional (CHT)

  • Korean (KOR)

  • Czech (CSY)

  • Dutch (NLD)

  • Polish (POL)

  • Portuguese (Portugal) (PTG)

  • Swedish (SWE)

  • Turkish (TUR)

  • Hungarian (HUN)

  • English (ENU)

  • 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:
  
  

  <machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

  
  Note Add the line under the <system.web> section, as described in the following article in the Microsoft Knowledge Base:
  
  

  911722 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.
  
  

  Registry location:HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse
  DWORD name: Bulk Insert Command Timeout Seconds
  
  DWORD Value: 40
  
  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:

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.

4. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

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.1015.

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\Microsoft System Center 2012 R2\Operations Manager\Server \SQL Script for Update Rollups\

4. Run the following SQL script on the Database Server against the OperationsManagerDWdatabase:
   
   

   UR_Datawarehouse.sql
   

5. 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

   • Microsoft.SystemCenter.Visualization.Component.Library.mpb

Learn about how to import a management pack from a disk.

Note Management packs are included in the Server component updates in the following path:

%SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups

Uninstall information

To uninstall an update, run the following command:

msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid Note In this command, PatchCodeGuid is a placeholder that represents one of the following GUIDs.

Additionally, RTMProductCodeGuid is a placeholder that represents one of the following GUIDs.

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

To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:

1. Apply Update Rollup 2 to your System Center 2012 R2 Operations Manager environment.

2. Download the updated management packs for System Center 2012 R2 from the following Microsoft website:
   
   

   System Center Monitoring Pack for UNIX and Linux Operating Systems

3. Install the management pack update package to extract the management pack files.

4. Import the updated Microsoft.Unix.Library management pack and the library management packs that are relevant to the Linux or UNIX platforms that you are monitoring in your environment.

5. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.

6. In the Administration pane of the Operations Console, upgrade each agent to the latest version by using either the Update-SCXAgent Windows PowerShell cmdlet or the UNIX/Linux Agent Upgrade Wizard.