Update Rollup 4 for System Center 2012 R2 Operations Manager

• 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 multi-language, 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 want to override the default BULK insert command timeout.
  
  

  Registry location:HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data WarehouseDWORD 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.

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.

Note If the Connected MG/Tiering feature is enabled, you should first update the top tier of the Connected MG/Tiering feature.

To download the update rollup package and extract the files that are contained in it, 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. Or download from Microsoft Update Catalog.

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 of 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 OperationsManagerDW database:
   
   

   UR_Datawarehouse.sql

   
   

5. Import the following management packs:

   • Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependency:

     • Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the System Center Operations Manager 2012 R2 media.

     
     

   • Microsoft.SystemCenter.Visualization.Library.mpb

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

   • Microsoft.SystemCenter.Advisor.mpb

   • Microsoft.SystemCenter.Advisor.Internal.mpb

   • Microsoft.SystemCenter.2007.mp

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\System Center 2012 R2\Operations Manager\Server\Management Packs for Update RollupsUNIX/Linux update

This update must be installed on all computers that have the Operations Manager console installed. Additionally, to apply this hotfix, you must have version 7.5.1025.0 or later of the UNIX/Linux Process Monitoring, UNIX/Linux Log File Monitoring, and UNIX/Linux Shell Command Template management pack bundles.

Management Pack bundle update
Note Follow the 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 4 to your System Center 2012 R2 Operations Manager environment.

2. Download the updated management packs for System Center 2012 R2.

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

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

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

To install the updated management packs for JEE application servers, follow these steps:

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

2. Download the updated UNIX/Linux management packs for System Center 2012 R2 from System Center Management Pack for UNIX and Linux Operating Systems.

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

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

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

6. Download the updated JEE application servers management packs for System Center 2012 R2 from System Center Management Pack for JEE application servers.

7. Install the management pack update to extract the management pack files.

Import the updated management pack for each version of the JEE application servers that you are monitoring in your environment.

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.

Operations Manager

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

Operations Manager - JEE Application Monitoring (Management Pack update)

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.