MS15-086: Security update for Update Rollup 10 for System Center 2012 Operations Manager Service Pack 1: August 11, 2015

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

Issues that are fixed in this update rollup

Operations Manager

  • The home page link on the Web Console noscript.aspx file is vulnerable to cross-site scripting (XSS)

    A security vulnerability exists in the Web Console for System Center 2012 Operations Manager SP1 that could allow elevation of privilege if a user visits an affected website by way of a specially crafted URL. This fix resolves that vulnerability. For more information, see Microsoft Security Bulletin MS15-086.

  • CLR load order change

    The current behavior for agents is to choose a CLR version based on the operating system version. For Windows Server 2012 and newer, the .NET Framework 4.0 is loaded. For operating systems older than Windows Server 2012, the .NET Framework 2.0 family is loaded. On management servers, the .NET Framework 2.0 family is loaded. This basically maps the .NET Framework version used to the version available out-of-box on the server. The problem with the current behavior is that even if the Management Pack author knows that .NET Framework 4.0 is present on the system it cannot be used.

    In the new behavior, the agent loads the .NET Framework 4.0 if it is available else it falls back to the .NET Framework 2.0.

  • p_GroomTypeSpecificLogTables does not groom all MT_*Log tables

    In a database, the grooming of certain MT$X$Y tables was missed because of the filtering logic. Therefore, the tables were never groomed. There were scenarios in which large amounts of unwanted data were stored in these tables. This issue is now fixed, and data from these tables will be groomed. This in turn will provide for performance gains because there will be less data to query from.

  • Branding update

    Updates the "Operational Insights" name to "Operations Management Suite" in the System Center Operations Management console.

How to obtain and install Update Rollup 10 for System Center 2012 Operations Manager SP1

Download information

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

Installation instructions

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 Multilanguage, 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 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 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 time-out issue that is described in Update Rollup 5 for System Center 2012 Operations Manager Service Pack 1 adds a registry key. This key 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 time-out.

    Registry location:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse

    DWORD name: Bulk Insert Command Timeout Seconds
    DWORD Value:nn

    Note The placeholder nn represents a value in seconds. For example, set the value data to 40 for a 40-second time-out.

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.

Operations Manager update
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. Execute the following Datawarehouse SQL script on Datawarehouse Server against OperationsManagerDW database:


    Note This script is located in the following path:

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

  4. Execute the following Database SQL script on the Database server against the OperationsManagerDB database:


  5. Import the following management packs:
    • Microsoft.SystemCenter.TFSWISynchronization.mpb. This has the following dependency:
      • Microsoft.SystemCenter.AlertAttachment.mpb. This should be installed from the System Center Operations Manager 2012 R2 media.
      • Microsoft.SystemCenter.Visualization.Library.mpb

    • Microsoft.SystemCenter.IntelliTraceProfiling.mpb, which has the following dependencies:
      • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb

        Note Install this file from the System Center Operations Manager (SCOM) 2012 SP1 Media.

      • Microsoft.Windows.InternetInformatonServices.Common.mpb

        Note Install this file from the online catalog.

    • Microsoft.SystemCenter.Visualization.Component.Library.mpb
    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Advisor.mpb
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.Advisor.Resources.LANGUAGECODE_3LTR.mpb
    • Microsoft.SystemCenter.Apm.Infrastructure.mpb
    • Microsoft.SystemCenter.Apm.Library.mpb

For information about how to import a management pack from a disk, see the How to Import an Operations Manager Management Pack topic on the Microsoft TechNet website.

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

UNIX and Linux Management Pack update
To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:
  1. Apply Update Rollup 8 to your System Center 2012 SP1 Operations Manager environment.
  2. Download the updated management packs for System Center 2012 SP1 from the following Microsoft website:

  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.

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:

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}

Files updated in this update rollup

The following is a list of files that have changed in this update rollup. If you do not have all previous update rollups installed, files other than those listed here may also be updated. For a complete list of files that are updated, refer to the "Files Updated in this Update Rollup" section of all update rollups that were released after your current update rollup.

Files that are updatedVersionSize
HealthServiceRuntime.dll7.0.9538.1136311 KB
Microsoft.EnterpriseManagement.UI.Administration.dll7.0.9538.11364.25 MB
Microsoft.EnterpriseManagement.UI.Administration.resources.dll7.0.9538.11362.41 MB
Microsoft.EnterpriseManagement.Presentation.WebConsole.dll 7.0.9538.1136106 KB
Microsoft.Mom.Common.dll 7.0.9538.1136255 KB
Microsoft.EnterpriseManagement.Monitoring.Console.exe7.0.9538.11364.45 MB
update_rollup_mom_db.sql7.0.9538.113662 KB

Article ID: 3071088 - Last Review: 08/12/2015 11:48:00 - Revision: 2.0

Microsoft System Center 2012 Operations Manager Service Pack 1

  • kbqfe kbsurveynew kbfix kbexpertiseinter atdownload kbsecvulnerability kbsecurity kbsecbulletin kbbug KB3071088