Update Rollup 11 for System Center 2012 R2 Operations Manager

Applies to: System Center 2012 R2 Operations Manager


This article describes the issues that are fixed in Update Rollup 11 for Microsoft System Center 2012 R2 Operations Manager. It also contains the installation instructions for this update.

Issues that are fixed in this update rollup

Operations Manager

  • Network discovery fails because of monitoring host crash if no paging file is set on the operating system

    When no paging file is set on the operating system, the page file size is implicitly set to 0. This causes the monitoring host to crash. This update fixes such an exception.

  • Backport PuTTY 0.64 and 0.66 updates from 2016 release

    Operations Managers ssh-based administration of UNIX/Linux computers (agent discovery and installation, upgrade, uninstallation) now supports UNIX and Linux computers that are configured to require SHA2 HMACs and those with Key Exchange Algorithm changes, as specified in RFC 4419 (Ubuntu 15.10, 16.04 LTS).

  • Update Register-SCAdvisor cmdlet for WEU workspaces

    This update adds support to register the Operations Manager Management group to workspaces in regions other than Eastern US by using the Register-SCAdvisor cmdlet. The cmdlet takes an additional optional parameter (SettingServiceUrl), which is the URL for setting the service in the region of the workspace. If it is not specified, the workspace is assumed to be in the Eastern US.

  • ACS eventschema.xml has incorrect parameter mappings for multiple audit events

    The report named Usage_-_Sensitive_Security_Groups_Changes used to say n/a\n/a for some events in the Changed By column. And in some events, the Member User column contained the account name of the user who made the change instead of the account that was added or removed. This fix resolves this issue, as the Changed By column now contains the account name of the user who made the change, and the Member User column contains the name of the added or removed account, where applicable.

  • Memory leak when monitoring network devices by using SNMPv3

    This update fixes a memory leak in Network Monitoring area that occurs while monitoring network devices by using SNMPv3.

  • Web Console user can view datawarehouse performance or SLA widget data outside of their scoped dashboard views

    This update implements verification of the logged-in user to confirm that the user has access to the opened dashboard before loading the same.

  • Downtime duration doesn't take business hour into consideration

    Business hours are being calculated even when the Business hours check box is cleared. This update resolves this issue.

    The updated RDL files are located in the following location:
    %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Reporting

    To update the RDL file, follow these steps:
    1. Go to http://MachineName/Reports_INSTANCE1/Pages/Folder.aspxMachineName //Reporting Server.
    2. On this page, go to the folder to which you want to add the RDL file. In this case, click Microsoft.SystemCenter.DataWarehouse.Report.Library.
    3. Upload the new RDL files by clicking the upload button at the top. For more information, see the Upload a File or Report (Report Manager) topic on the Microsoft Developer Network website.

  • Cisco 3172 PQ network device certification issues

    This update fixes issues in monitoring the Cisco 3172 PQ network device and its components.

  • Adding SCOM assessment links in the Operations Management Suite view in the SCOM console

    Links for Operations Manager Assessment and Pre-Configuration steps for Operations Manager Assessment are added in the Operations Management Suite Connection node under the administration pane. SCOM assessment solution in OMS is currently in private preview, please reach out to your "TAM or other Microsoft contact" to obtain access to the solution.

  • SQL Server Seed relationship with a server that is running Windows

    The dynamic members of the group are not populated if the dynamic rule is based on a hosted relationship with Windows Server. This fix enables retrieval of hosting entity.

  • Alert subscriptions are not always fired for 3 state monitors

    This update allows for configuration of a 3 state monitor to raise alerts; whose severity is in sync with monitor’s health state. One can create a subscription to be notified on modification of alert severity. Even if the monitor’s state keeps toggling between warning and critical, severity of the alert keeps being updated, and a notification fired on an update to the severity of an alert.

  • When you connect SCOM to OMS, Availability monitors health state of some management servers changes to Warning state

    If OMS workspace is configured to collect certain event logs and if those event logs are not present on the management servers that are connected to that workspace, the “Availability” monitor’s health state on those management servers that are used to change the Warning state. This state change scenario is fixed. This prevents the switch to Warning state.

  • RunAs Account password expiration does not work with Active directory Password Settings Objects that breaks the validation of LOCAL User Accounts

    Local Accounts could not be validated by using ADSystemInfo. Therefore, when any local account is added into RunAs account, an Error event is logged in Event Viewer for an exception in validating the local account. After this update, local accounts are validated.

  • MPB Entries in Catalog database for the VersionIndependentGuid column is updated

    This update enables the SCOM console to show the correct mpb installation status in the management server when it tries to connect to an online catalog to update mpbs.

  • If the first try of importing MPB failed then re-importing the MPB was not possible until the SCOM console is closed and reopened

    This update enables re-download and installation of an mpb, without closing and reopening the SCOM console, even if the first try installation of that mpb failed because of a dependency issue.

  • Change of the displayname field for a group in a sealed or unsealed management pack

    Renaming a group through PowerShell cmdlets was not displaying the new group name in the SCOM console. This update resolves this issue and the renaming of a group correctly displays the renamed group name in the SCOM console.

New Linux operating system versions supported

  • Ubuntu Linux 16.04 LTS (x86 and x64) is now supported in System Center 2012 R2 Operations Manager.

Issues that are fixed in the UNIX and Linux management packs

  • During UNIX/Linux computer discovery, the GetOSVersion.sh script is run with sudo elevation if a sudo-enabled user is selected for Discovery. This update prevents the GetOSVersion.sh script from being run with sudo elevation and does not have to be authorized in the /etc/sudoers folder.

  • Scripts executed by the ExecuteScript method in Management Packs always run from the /tmp folder. With this update, the temporary folder for scripts is now configurable. To use another folder, update the symbolic link to link to a temporary folder of your choice:

  • UNIX or Linux computers together with sshd versions that implement the Key Exchange Algorithms described in RFC 4419, such as Ubuntu 15.10, cannot be discovered with the Discovery Wizard.

  • Network statistics collected on AIX servers are reset when another tool such as NetStat is also used.

  • Physical disks are shown incorrectly as offline if an LVM snapshot is taken.

How to obtain and install Update Rollup 11 for System Center 2012 R2 Operations Manager

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 Operational 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 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 time out issue described in Update Rollup 1 for System Center 2012 R2 Operations Manager 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 Time Out 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
    • Audit Collection Services
    • 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. Or download from the Microsoft Download 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. Execute the flowing Datawarehouse SQL script on Datawarehouse Server against OperationsManagerDW database:


    Note This script is located in the following path:

    %SystemDrive%\Program Files\System Center 2012 R2\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, 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.Visualization.Library.mpb
    • Microsoft.SystemCenter.Advisor.mpb
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.2007.mp
    • Microsoft.SystemCenter.Advisor.Resources.LANGUAGECODE_3LTR.mpb
    • Microsoft.SystemCenter.SyntheticTransactions.Library.mp
    • Microsoft.SystemCenter.OperationsManager.Library.mp
    • Microsoft.SystemCenter.OperationsManager.Internal.mp
    • Microsoft.SystemCenter.Apm.Web.IIS10.mp which has the following dependency:
    • Microsoft.SystemCenter.ClientMonitoring.Internal.mp which has the following dependency:
      • Microsoft.SystemCenter.ClientMonitoring.Library.mp
      • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
      • Microsoft.SystemCenter.ClientMonitoring.Views.Internal.mp

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

UNIX/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 11 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:

  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.