Tell me about the issue and I’ll help you find the solution you need.
MS15-086: Security update for Update Rollup 10 for System Center 2012 Operations Manager Service Pack 1: August 11, 2015
Content provided by Microsoft
Applies to: Microsoft System Center 2012 Operations Manager Service Pack 1
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
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.
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
Update packages for Operations Manager are available from Microsoft Update or by manual download.
To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an Operations Manager component installed:
Click Start, and then click Control Panel.
In Control Panel, double-click Windows Update.
In the Windows Update window, click Check Online for updates from Microsoft Update.
Click Important updates are available.
Select the Update Rollup package, and then click OK.
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:
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.
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:
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.
Operations Manager update
To download the update rollup package and extract the files that are contained in the 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.
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
Execute the following Database SQL script on the Database server against the OperationsManagerDB database:
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.IntelliTraceProfiling.mpb, which has the following dependencies:
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.