Description of Update Rollup 6 for System Center 2012 Operations Manager Service Pack 1

Applies to: Microsoft System Center 2012 Operations Manager Service Pack 1


This article describes the issues that are fixed in Update Rollup 6 for Microsoft System Center 2012 Service Pack 1 (SP1) Operations Manager and the Linux and Unix Monitoring Pack. Additionally, this article contains the installation instructions for Update Rollup 6 for System Center 2012 SP1 Operations Manager.

Issues that are fixed in this update rollup

Operations Manager

Issue 1

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 2

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

Issue 3

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

Issue 4

Adding multiple regular expressions (RegEx's) to a group definition causes a SQL exception when adding or running the group.

Issue 5

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

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 obtain and install Update Rollup 6 for System Center 2012 Operations Manager SP1

Download instructions

Update packages for Operations Manager are available from Microsoft Update or by manual download.

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 SP1 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 packages, and then click OK.
  6. To to install the update package, click Install updates.
Manual download of the update packages
To manually download the update packages, go to the following Microsoft Update Catalog website:

Installation instructions for Operations Manager

Known issues for this update
  • After you install this update rollup package on all roles on the server that is running System Center Operations Manager 2012 Service Pack 1 (except on the Agent and Gateway roles), the updates do not appear in the Add or Remove Programs item in Control Panel.
  • After you apply Update Rollup 6, the Operations Manager console must be reopened in order to apply the Alert Attachment Management Pack fix.
  • After you install this update rollup package, the version number of the console is not changed.
  • If the ACS update package is installed, uninstalled, and then re-installed, the database upgrade script that is included in this update does not run. This is because the database version is changed during the first installation of the ACS update. This issue can cause a server crash if the user reuses a partition when the partition is in use. The partition can be closed manually by using SQL Server Studio. To do this, navigate to the ACS database, and then run the following script in a query editor window:

    begin tran  -- mark all active partitions for closing if (select count(*) from dtPartition where Status = 0) > 0 update dtPartition set Status = 1 where Status = 0  commit tran

    To create a new partition, stop AdtServer, run the script, and then start AdtServer again.
  • After you install the update rollup package on a web console, you may receive the following error message in Internet Explorer:

    Server Error in '/OperationsManager' Application.

    To resolve this issue, close and then restart Internet Explorer.

  • 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 the 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 the update rollup package immediately after you install the System Center 2012 SP1 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.
  • After you install the web console update, 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 time-out issue described in the Update Rollup 5 for System Center 2012 Service Pack 1 article adds a registry key that can be used to set the time-out value (in seconds) for the data warehouse BULK insert commands. The following are the commands that insert new data into the data warehouse.

    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 For example, the value name should be set to 40 for a 40 second timeout.
Supported installation order
We recommend that you install the update rollup package by following these steps in the given order.
  1. Install the available update rollup package on the following server infrastructure:
    • Management server or servers
    • Gateway servers
    • ACS
    • Web console server role computers
    • Operations console role computers
  2. Manually import the management packs.
  3. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

  • Install the update rollup package on agents either before or after you install the update rollup package on the server infrastructure.
  • If the Connected MG/Tiering feature is enabled, you should first update the top tier of the Connected MG/Tiering feature.
  • Update Rollup 6 files have a version number of 9538.1109.
Installation information
To download the update rollup package and extract the files that are contained in the 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 Datawarehouse SQL script on the Datawarehouse Server against the OperationsManagerDW database:
    • UR_Datawarehouse.sql

    The path to this script is as follows:

    %SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server \SQL Script for Update Rollups

  4. Run the following Database SQL script on the Database server against the OperationsManagerDB database:
    • Update_rollup_mom_db.sql
  5. Import the following management pack:
    • Microsoft.SystemCenter.AlertAttachment.mpb
    • Microsoft.SystemCenter.IntelliTraceProfiling.mpb, which has the following dependencies:
      • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb (which should be installed from SCOM 2012 SP1 Media)
      • Microsoft.Windows.InternetInformationServices.Common.mpb (which should be installed from the online catalog)
    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.Apm.Infrastructure.mpb
    • Microsoft.SystemCenter.Apm.Library.mpb
    • Microsoft.SystemCenter.TFSWISynchronization.mpb
    • Microsoft.SystemCenter.Visualization.Component.Library.mpb

Learn about How to Import an Operations Manager Management Pack.

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

%SystemDrive%\Program Files\System Center 2012 SP1\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.

PatchCodeGuid ComponentArchitectureLanguage
{E765288E-B1D9-4939-BF8B-0507CDDB771A}ACS AMD64CS
{A03149FE-D8A4-4C0E-B2D5-03D6D27F1386}ACS AMD64DE
{2F242A84-66A0-4C7C-A89E-0A8C2A8C3F59}ACS AMD64ES
{D6F36BE7-E5B1-436F-B06A-5CD78D6B1DD2}ACS AMD64HU
{C4A01548-03B9-4DDC-8555-DDFE8ABD4B21}ACS AMD64IT
{2DDFA903-4D31-4122-9CC3-C46F838C431D}ACS AMD64JA
{5338D1F2-400B-4713-941C-4CA3C70AB7CC}ACS AMD64KO
{FA97260C-27B4-424A-B460-00AE9372F03B}ACS AMD64NL
{DFCD60B9-EE32-4EFC-8006-0C1D5746E52D}ACS AMD64PL
{61BCD312-2283-448F-8678-629A1ACA0E55}ACS AMD64PT-BR
{F4EE6AFE-1797-4AA1-A454-A6E6E13CC2C7}ACS AMD64PT-PT
{F9359D9F-2855-476F-A7CB-82A7B8CB05AA}ACS AMD64RU
{DDB1A676-12C7-4772-A14D-27B1BD1EAA8B}ACS AMD64SV
{272C24D4-916C-4459-B1C7-91C5270DB300}ACS AMD64TR

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

Console (AMD64){5142AB0B-73E3-4AD3-9D0F-65B3D9026769}
Console (x86){358C8AF0-25BB-425A-A4E6-7ADE54ED4736}
WebConsole (AMD64){5ED945BA-2BDD-4567-804E-8D3D2DB5CC9B}
Agent (AMD64){8B21425D-02F3-4B80-88CE-8F79B320D330}
Agent (x86){387306D9-78CE-4E0E-B952-28A50CC8B3EE}
Agent (IA-64){F3DDB021-89BC-464F-9107-69E2547D08FD}
SCX-ACS (AMD64){B30F4F71-2AF3-4542-855B-E1C7A31AC9A5}
SCX-ACS (x86){B30F4F71-2AF3-4542-855B-E1C7A31AC9A5}

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. Download the updated management packs from the following Microsoft website:

  2. Install the management pack update package to extract the management pack files.
  3. Import the updated Microsoft.Unix.Library management pack (from the \2012 SP1\ folder), Microsoft.ShellCommand.Library management pack bundle, Microsoft.Process.Library management pack bundle, and platform library management packs relevant to the Linux or UNIX platforms that you are monitoring in your environment.
  4. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
  5. Restart the "System Center Management Service" on each Management Server or Gateway that is used to manage UNIX/Linux agents.
  6. 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.

Note The management pack bundle files for each UNIX and Linux operating system version contain the management pack and agent files. You may have to wait several minutes after you import the management pack bundle before the agent files are available for agent upgrades.

Files updated in Update Rollup 6 packages