Update Rollup 8 for System Center 2012 R2 Operations Manager

Introduction

This article describes the issues that are fixed in Update Rollup 8 for Microsoft System Center 2012 R2 Operations Manager. Additionally, this article contains the installation instructions for Update Rollup 8 for System Center 2012 R2 Operations Manager.

Issues that are fixed in this update rollup

Operations Manager

  • Slow load of alert view when it is opened by an operator
    Sometimes when the operators change between alert views, the views take up to two minutes to load. After this update rollup is installed, the reported performance issue is eradicated. The Alert View Load for the Operator role is now almost same as that for the Admin role user.

  • SCOMpercentageCPUTimeCounter.vbs causes enterprise wide performance issue
    Health Service encountered slow performance every five to six (5-6) minutes in a cyclical manner. This update rollup resolves this issue.

  • System Center Operations Manager Event ID 33333 Message: The statement has been terminated.
    This change filters out "statement has been terminated" warnings that SQL Server throws. These warning messages cannot be acted on. Therefore, they are removed.

  • System Center 2012 R2 Operations Manager: Report event 21404 occurs with error '0x80070057' after Update Rollup 3 or Update Rollup 4 is applied.
    In Update Rollup 3, a design change was made in the agent code that regressed and caused SCOM agent to report error ‘0x80070057’ and MonitoringHost.exe to stop responding/crash in some scenarios. This update rollup rolls back that UR3 change.

  • SDK service crashes because of Callback exceptions from event handlers being NULL
    In a connected management group environment in certain race condition scenarios, the SDK of the local management group crashes if there are issues during the connection to the different management groups. After this update rollup is installed, the SDK of the local management group should no longer crash.

  • Run As Account(s) Expiring Soon -- Alert does not raise early enough
    The 14-day warning for the RunAs account expiration was not visible in the SCOM console. Customers received only an Error event in the console three days before the account expiration. After this update rollup is installed, customers will receive a warning in their SCOM console 14 days before the RunAs account expiration, and receive an Error event three (3) days before the RunAs account expiration.

  • Network Device Certification
    As part of Network device certification, we have certified the following additional devices in Operations Manager to make extended monitoring available for them:

    • Cisco ASA5515

    • Cisco ASA5525

    • Cisco ASA5545

    • Cisco IPS 4345

    • Cisco Nexus 3172PQ

    • Cisco ASA5515-IPS

    • Cisco ASA5545-IPS

    • F5 Networks BIG-IP 2000

    • Dell S4048

    • Dell S3048

    • Cisco ASA5515sc

    • Cisco ASA5545sc

  • French translation of APM abbreviation is misleading
    The French translation of “System Center Management APM service” is misleading. APM abbreviation is translated incorrectly in the French version of Microsoft System Center 2012 R2 Operations Manager. APM means “Application Performance Monitoring” but is translated as “Advanced Power Management." This fix corrects the translation.

  • p_HealthServiceRouteForTaskByManagedEntityId does not account for deleted resource pool members in System Center 2012 R2 Operations Manager
    If customers use Resource Pools and take some servers out of the pool, discovery tasks start failing in some scenarios. After this update rollup is installed, these issues are resolved.

  • Exception in the 'Managed Computer' view when you select Properties of a managed server in Operations Manager Console
    In the Operations Manager Server “Managed Computer” view on the Administrator tab, clicking the “Properties” button of a management server causes an error. After this update rollup is installed, a dialog box that contains a “Heart Beat” tab is displayed.

  • Duplicate entries for devices when network discovery runs
    When customers run discovery tasks to discover network devices, duplicate network devices that have alternative MAC addresses are discovered in some scenarios. After this update rollup is installed, customers will not receive any duplicate devices discovered in their environments.

  • Preferred Partner Program in Administration Pane
    This update lets customers view certified System Center Operations Manager partner solutions directly from the console. Customers can obtain an overview of the partner solutions and visit the partner websites to download and install the solutions.

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

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

Windows Update

To obtain and install an update package from Windows 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.

Microsoft Update Catalog

This update package is available for manual download and installation from the Microsoft Update Catalog:

Download Download the Operations Manager update package now.

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 this line in 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 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. The following commands 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: 40

    Note Set this value in seconds. For example, for a 40-second time-out, set this value to 40.

Supported installation orderWe 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.

Operations Manager UpdateTo 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:

    UR_Datawarehouse.sql

    Note This script is located in the following path:

    %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups

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

    Update_rollup_mom_db.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.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


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 UpdateTo install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:



  1. Apply Update Rollup 7 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:

    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.



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

Component

Architecture

Language

{F8B891F3-6102-427C-A3F1-607196F572F7}

Agent

amd64

en

{E2792223-E343-4528-AE04-E1879DE7B3B5}

Console

amd64

en

{9140E578-AA40-438C-920A-0C09B735B40E}

WebConsole

amd64

en

{74D53408-88F1-4465-AF0C-2640485CB52A}

Gateway

amd64

en

{B2491E23-6248-4045-9D3C-C0D18CB3E3F4}

Server

amd64

en

{B1D8B0B2-8373-4D98-A864-5A3EA9F9EF52}

Agent

x86

en

{3998D55E-112C-4158-8B3F-1ADA405E956E}

Console

x86

en

{C2381E7C-8586-4204-8288-C3B5EFC8ADF8}

Console

amd64

cn

{3EB81E4D-CDA8-4ED7-9430-ED861616F806}

WebConsole

amd64

cn

{5722D1B0-5900-4E09-9D08-EF0A66178869}

Console

x86

cn

{D43F958B-C55B-4612-A75F-F227C560F17A}

Console

amd64

cs

{5DAF8370-0378-4CC1-A52C-B6A909C2F618}

WebConsole

amd64

cs

{3BA7C8F9-88E8-4B20-AFE0-86EE45E99ACF}

Console

x86

cs

{707AE029-016B-48AD-AE2C-06F0F9B8D8A0}

Console

amd64

de

{3DC8B2C5-2011-4176-AA76-407FD180C26D}

WebConsole

amd64

de

{FC17D0CC-5417-4415-9F73-F2792D2B7031}

Console

x86

de

{02B8530A-C34C-4A7E-AAFD-7F080AD954C3}

Console

amd64

es

{DB54E984-FC9D-4233-A20A-B866228B5E7C}

WebConsole

amd64

es

{AB67C0E6-AAFD-44F7-B884-314B435DAE9F}

Console

x86

es

{454C7CB8-C238-4881-ADAA-A5A505593A4C}

Console

amd64

fr

{E979F910-57CD-418C-B796-AF60CF442D1F}

WebConsole

amd64

fr

{3F12984E-CB31-4E74-BCEA-3D20F767C4B1}

Console

x86

fr

{501C1461-915D-4EA1-83B2-A4C1EB5F6D1C}

Console

amd64

hu

{72B587E3-CE3C-4B03-9452-4DD62325F225}

WebConsole

amd64

hu

{A81A1754-58FC-4425-9484-32AE8E366187}

Console

x86

hu

{6C76B77C-D9D0-4E8A-B72A-8E10029EFF9E}

Console

amd64

it

{45B51EAE-D1F6-4672-82EB-09D020E38B41}

WebConsole

amd64

it

{A1BF0055-D9D1-4FE9-BEA7-C4FF1794B428}

Console

x86

it

{2133708F-B7E2-4F24-AC5D-74F3E332A9C7}

Console

amd64

ja

{9DDEB7CB-440E-4470-81C9-B518BE57B372}

WebConsole

amd64

ja

{A19EFA12-649C-4B31-9753-AE9419C8C517}

Console

x86

ja

{10FF5DFD-BC00-400E-9510-F92E0A8F2A56}

Console

amd64

ko

{2DA4CCEC-FED4-42A5-8247-124A83FB36B5}

WebConsole

amd64

ko

{77EB2B21-E959-45B9-997C-4CCB8670FDCC}

Console

x86

ko

{91BA199E-4A07-4C98-B345-8D857DE1466D}

Console

amd64

nl

{6CF4AD09-6D5F-42A8-9BFD-004AE64481DB}

WebConsole

amd64

nl

{B39BBF00-6716-438A-959E-DCA10FCEEBAA}

Console

x86

nl

{99751571-2597-41BE-8EFC-CBD5EE61CA48}

Console

amd64

pl

{06C83C5C-5122-4304-BF62-B859847809DE}

WebConsole

amd64

pl

{AD748E4D-B90D-44B6-9E2B-B11293878577}

Console

x86

pl

{D915FB33-1654-48C7-86A9-9EB668BFC445}

Console

amd64

pt-br

{7E30A061-0E19-4CF5-B129-29956FE00134}

WebConsole

amd64

pt-br

{FDF79143-5516-4EF3-9557-1C2C2498C438}

Console

x86

pt-br

{4693A703-BE4D-4796-AFFC-920BEE4B86DB}

Console

amd64

pt-pt

{4CD98779-ECAD-4B07-B0B8-9D9D6641A144}

WebConsole

amd64

pt-pt

{11FCC5E8-60FA-4833-B1FE-8D6954636C6E}

Console

x86

pt-pt

{951767AD-3C97-4EB2-97B4-3C202AAA03CD}

Console

amd64

ru

{83F43650-0804-4C05-9E40-F1102DD5E5F1}

WebConsole

amd64

ru

{D2924DD0-A01D-45A8-A752-471BF8D55A07}

Console

x86

ru

{BAF50AA4-DEEE-4C90-A268-9E2217777B78}

Console

amd64

sv

{FEEE6C18-7C82-4FEA-9F41-56430B5F837E}

WebConsole

amd64

sv

{4BEF4BB3-8E2D-407D-835E-4C9A983151FB}

Console

x86

sv

{E624D0F4-C862-4C26-9ADB-6AB894837F97}

Console

amd64

tr

{03CD618E-FA45-4EB5-A23F-927FA5B78098}

WebConsole

amd64

tr

{8ECB2EE6-D873-4128-B36A-D9E4CC5ED045}

Console

x86

tr

{FCB5819D-8D1B-42FF-9837-0C3DC37691C8}

Console

amd64

tw

{5CF187E6-A5E6-4CFB-8CDD-530127FB1FEB}

WebConsole

amd64

tw

{E8574713-C478-4713-8B6F-C7B8AC703A49}

Console

x86

tw

{B20D9C92-9C6E-4E58-A37D-964664A3905E}

Console

amd64

zh-hk

{C48805A1-B497-46A7-B080-A5950B87F710}

WebConsole

amd64

zh-hk

{F8122212-38D2-4C50-848A-BD38F8F02733}

Console

x86

zh-hk


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

Component

RTMProductCodeGuid

Server

{C92727BE-BD12-4140-96A6-276BA4F60AC1}

Console (AMD64)

{041C3416-87CE-4B02-918E-6FDC95F241D3}

Console (x86)

{175B7A24-E94B-46E5-A0FD-06B78AC82D17}

WebConsole (AMD64)

{B9853D74-E2A7-446C-851D-5B5374671D0B}

Gateway

{1D02271D-B7F5-48E8-9050-7F28D2B254BB}

SCX-ACS (AMD64)

{46B40E96-9631-11E2-8D42-2CE76188709B}

SCX-ACS (x86)

{46B40E96-9631-11E2-8D42-2CE76188709B}

Agent (AMD64)

{786970C5-E6F6-4A41-B238-AE25D4B91EEA}

Agent (x86)

{B4A63055-7BB1-439E-862C-6844CB4897DA}


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 updated

Version

Size

mommodules.dll

7.1.10241.0

2.5 MB

InterceptSvc.exe

7.1.10241.0

612 KB

Microsoft.EnterpriseManagement.DataAccessService.OperationsManager.dll

7.1.10226.1118

571 KB

MonitoringHost.exe

7.1.10241.0

29 KB

HealthServicePerformance.dll

7.1.10241.0

41 KB

HealthService.exe

7.1.10241.0

25 KB

AgentConfigManager.dll

7.1.10241.0

132 KB

AgentControlPanel.exe

7.1.10241.0

724 KB

ApmConnector.dll

7.1.10241.0

64 KB

MOMScriptAPI.dll

7.1.10241.0

671 KB

MOMConnector.dll

7.1.10241.0

687 KB

HealthService.dll

7.1.10241.0

3.16 MB

MomIISModules.dll

7.1.10241.0

557 KB

NetworkDiscoveryModules.dll

7.1.10226.1118

385 KB

SnmpModules.dll

7.1.10241.0

471 KB

XmlStringToDataItemModule.dll

7.1.10241.0

121 KB

MOMConnectorPerformance.dll

7.1.10241.0

32 KB

HSLockDown.exe

7.1.10241.0

95 KB

EventCommon.dll

7.1.10241.0

386 KB

ServiceConnector.dll

7.1.10241.0

165 KB

HealthServiceRuntime.dll

7.1.10241.0

313 KB

MOMModules2.dll

7.1.10241.0

243 KB

SCOMMaintenanceMode.dll

7.1.10241.0

72 KB

MomNetworkModules.dll

7.1.10241.0

765 KB

Microsoft.Mom.UI.Common.dll

7.1.10226.1118

2.19 MB

Microsoft.EnterpriseManagement.UI.Administration.dll

7.1.10226.1118

4.26 MB

Microsoft.EnterpriseManagement.UI.Administration.resources.dll

7.1.10226.1118

2.41 MB

Microsoft.Mom.UI.Components.dll

7.1.10226.1118

5.87 MB

Microsoft.EnterpriseManagement.DataAccessLayer.dll

7.5.3079.502

2.4 MB

ic-iftable.asl

7.1.10226.1118

21 KB

ic-ip-address.asl

7.1.10226.1118

19 KB

oid2type_Cisco.conf

7.1.10226.1118

399 KB

oid2type_F5.conf

7.1.10226.1118

8 KB

oid2type_force10.conf

7.1.10226.1118

9 KB

Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb

7.1.10226.1107

72 KB

Microsoft.SystemCenter.Advisor.mpb

7.1.10226.1118

348 KB

Microsoft.SystemCenter.2007.mp

7.1.10226.1118

423 KB

Microsoft.SystemCenter.OperationsManager.Internal.mp

7.1.10226.1118

71 KB

Microsoft.SystemCenter.OperationsManager.Library.mp

7.1.10226.1118

20 KB

update_rollup_mom_db.sql

7.1.10226.1118

154 KB


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×