Introduction

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

Issues that are fixed in this update rollup

Operations Manager

  • The Health Service bouncing that is caused by high memory usage in the MonitoringHost process.

  • This update includes a fix to prevent resynchronization of all managed entities from the Operations Manager to the Operations Manager Data Warehouse (OMDW) database and to prevent the failure to sync that this causes because of duplicate entries. The duplicate entries cause the following exception to occur:

    Description:
    Data was written to the Data Warehouse staging area but processing failed on one of the successive operations.
    Exception 'SqlException': Sql execution failed. Error 2627, Level 14, State 1, Procedure ManagedEntityChange, Line 367, Message: Violation of UNIQUE KEY constraint 'UN_ManagedEntityProperty_ManagedEntityRowIdFromDAteTime'. Cannot insert duplicate key in object 'dbo.ManagedEntityProperty'.


  • The import of Visualization.component.library and Visualization.library binary files (.mpb) fails. The import succeeds on a successive try.

  • System Center Operations Manager agents randomly time out when authenticating to the Gateway or Management Server because of domain controller or network performance issues. The time-out value was set to 1 second earlier. A fix was made to increase server time out to-20 seconds and client time out to 5 minutes.


For issues that were fixed in previous update rollups that are included in this rollup, see the following articles in the Microsoft Knowledge Base:

Supported operating systems

The following new Linux operating system version is supported:

Operating system

Management pack

Red Hat Enterprise Linux 7 (x64)

New Microsoft.Linux.RHEL.7.mpb



How to obtain and install Update Rollup 8 for System Center 2012 Service Pack 1

Download information

The 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 package, and then click OK.

  6. Click Install updates to install the update package.

Manual download of the update package

The following file is available for manual download from the Microsoft Update Catalog:

Download Download the Operations Manager update package now.

  • 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 the update rollup as an administrator.

  • If you do not want to restart the computer after you apply the console update, you should 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, you should 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"/>To learn about how to add a line to the <system.web> section of the web.config file, see the "Workaround" section of 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 describes a registry key that the user can add to set the time-out (in seconds) for the data warehouse bulk insert commands. The following is the registry setting that controls the time-out value when new data is inserted into the data warehouse.

    The registry subkey is as follows:

    Registry key:HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse
    DWORD Name: Bulk Insert Command Timeout Seconds
    Value data: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 servers

    • Gateway servers

    • Web Console Server role computers

    • Operations Console role computers

  2. Apply SQL scripts. (See the installation information for the update.)

  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.

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 Datawarehouse server against the OperationsManagerDW database:

    • UR_Datawarehouse.sql



    Note The path of the 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 packs:

    • Microsoft.SystemCenter.AlertAttachment.mpb

    • Microsoft.SystemCenter.IntelliTraceProfiling.mpb

      Note This pack has the following dependencies:

      • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb. This should be installed from SCOM 2012 SP1.

      • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb. This should be installed from the Microsoft Online Catalog.


    • Microsoft.SystemCenter.Visualization.Library.mpb

    • Microsoft.SystemCenter.Image.Library.mp

    • Microsoft.SystemCenter.Advisor.Internal.mpb

    • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp

    • Microsoft.SystemCenter.Apm.Infrastructure.mpb

    • Microsoft.SystemCenter.Apm.Library.mpb

    • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp

    • Microsoft.SystemCenter.DataWarehouse.Reports.mp

    • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp

    • Microsoft.SystemCenter.TFSWISynchronization.mpb

    • Microsoft.SystemCenter.Visualization.Component.Library.mpb


Learn about how to import a management pack from a disk.

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

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:

    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 RTMProductCodeGUIDNote In this command, the PatchCodeGUID placeholder represents one of the following GUIDs.

PatchGUID

Components

Architecture

Language

{ACCCA3CD-B4CB-4F6F-9680-EB0E5BFA2D23}

ACS

AMD64

CN

{8D28E860-4EA6-46EE-9CFB-767C0BECFAC0}

Console

AMD64

CN

{B99E2FA9-1537-4A16-AD8F-692DD73E9F2F}

WebConsole

AMD64

CN

{B42E0D94-9272-4A97-83DC-2646309427DC}

Console

x86

CN

{390CC3FE-6258-4062-87E6-D09548C1371A}

ACS

AMD64

CS

{CB2D8A28-2717-4D20-BAE7-4B628534CBE4}

Console

AMD64

CS

{1753A3A4-EC4D-4F62-8B0E-733B06BF4B88}

WebConsole

AMD64

CS

{7D0270D1-71A0-49AA-A38A-842747859963}

Console

x86

CS

{12585CE3-B87B-440C-937F-CC90C10177BB}

ACS

AMD64

DE

{1FF9AF78-93F0-4069-B512-5B14EF3C4650}

Console

AMD64

DE

{712DCE4A-4CE7-45B8-B631-90A5556ACDB5}

WebConsole

AMD64

DE

{637B77C6-BCC3-48FA-B80C-0294254720A5}

Console

x86

DE

{182F2214-3E3D-4058-BEDC-9125E64D1882}

Agent

AMD64

EN

{18960B77-E8F5-4CC0-91C0-84AF7E3516E3}

ACS

AMD64

EN

{213E19BC-94E3-4B3C-BE3F-59C612474F00}

Console

AMD64

EN

{55077A58-AC73-4DFE-9296-C63D2E68256C}

WebConsole

AMD64

EN

{06F3015A-7317-4557-B58B-CC5DEF752DE8}

Gateway

AMD64

EN

{AB984520-C786-4E47-95A2-22880249B91E}

Server

AMD64

EN

{A6646DA7-0299-4C5E-9966-A7BABBD5471C}

Agent

x86

EN

{1CC3E8DA-48DF-4968-BAB5-BBA61024E8C2}

Console

x86

EN

{B38769F3-1445-450A-B044-6D257FB88A9B}

Agent

IA-64

EN

{716A607D-E7C4-4C62-A99C-13C33BD1D83F}

ACS

AMD64

ES

{E4090C87-F646-4033-9DB5-12C7B8D27AEF}

Console

AMD64

ES

{01D2D7C0-05F8-4B42-9E79-64605C43FA75}

WebConsole

AMD64

ES

{DF150BE8-7C89-40C7-B77E-6AB3E048099E}

Console

x86

ES

{0F0FA9D7-2CB8-47DD-AC3A-7ADA39DB2DE2}

ACS

AMD64

FR

{750BB629-EFB9-4D14-ABCD-D5FFB751EB7B}

Console

AMD64

FR

{D4C2E95D-105D-4786-8D70-FCF5F439BFCD}

WebConsole

AMD64

FR

{29B9C7E2-7222-41E1-A1AD-F4026851ED09}

Console

x86

FR

{87F1F5D4-32C3-4698-807A-D3E3500D7C3C}

ACS

AMD64

HU

{B70EA6EC-DCF8-4908-9A3F-7F04395BA9F6}

Console

AMD64

HU

{334E2F5C-6153-4096-A407-620822906EFA}

WebConsole

AMD64

HU

{A9F25148-6B1E-4398-B835-AF2E5DE51573}

Console

x86

HU

{F3608ED3-C50B-492B-99FE-900C9656A9AB}

ACS

AMD64

IT

{8FDEBE95-C999-43D0-9624-9B7DF6CCD4DF}

Console

AMD64

IT

{57142171-814A-4A92-A7F3-7A1D62049B05}

WebConsole

AMD64

IT

{9ADD9240-78AC-4ACD-AC7D-357D896CAE33}

Console

x86

IT

{CE1CF9D1-6BFF-42D9-A0CC-FC2E0FEA1459}

ACS

AMD64

JA

{69961A16-3BEF-4403-90B4-1E6B0E2557CF}

Console

AMD64

JA

{69DDFB07-CC29-4F6E-814B-C1207B30C81C}

WebConsole

AMD64

JA

{F57449B5-F135-4BC9-A319-9EFBE18329E5}

Console

x86

JA

{D0991F55-733E-43F6-B253-FB0EB7790AA7}

ACS

AMD64

KO

{48953BED-30CE-432C-83F5-60C7A382FEBE}

Console

AMD64

KO

{2CC7E1F5-567A-4605-A293-6F92E25DFF5E}

WebConsole

AMD64

KO

{C6E39651-4CB4-4CF3-B3BB-74FC96A20A57}

Console

x86

KO

{88CCB591-D418-4839-AA1B-2763083014D7}

ACS

AMD64

NL

{5B3895B9-85BA-4D13-B954-E2C185FC2948}

Console

AMD64

NL

{54E19A16-1809-4A92-87C0-4C0B5BD01EA1}

WebConsole

AMD64

NL

{307A4D0A-DC99-46E3-BC13-82F2985F0927}

Console

x86

NL

{B2987E41-794B-4A40-AD59-CE623B29822B}

ACS

AMD64

PL

{4606BCE8-DC38-43C3-8B40-5588D55C7F8B}

Console

AMD64

PL

{6144EAA9-D769-4AAD-A7ED-310F57AE81C7}

WebConsole

AMD64

PL

{C6EAB03E-D1EE-4819-A196-4FCB0C6438E4}

Console

x86

PL

{9A8FA27A-61DC-460C-B216-377CAB36373D}

ACS

AMD64

PT-BR

{42C9DEA6-E678-4314-B7F5-2D153FD82B6C}

Console

AMD64

PT-BR

{9670ED69-0234-40D9-9E58-33265CA36D2E}

WebConsole

AMD64

PT-BR

{B0D5F155-3123-452C-A801-F935DFC4727F}

Console

x86

PT-BR

{DF62851C-0AD0-4E69-B609-522BF966F0C0}

ACS

AMD64

PT-PT

{FFE092B0-8FFC-4FC4-9C67-03DBABBA50ED}

Console

AMD64

PT-PT

{37093F69-B9FE-4830-B2F2-D39EA3BC3115}

WebConsole

AMD64

PT-PT

{B8BBAD5E-B9C3-482B-8927-FFF1E1D44A0C}

Console

x86

PT-PT

{5A8BAD0E-F2B6-4097-81A8-0B597233DFAE}

ACS

AMD64

RU

{B679AE41-360E-4967-A200-34A2B1DCB687}

Console

AMD64

RU

{A631B62F-7284-4B5A-BDE9-CEDDA4063E83}

WebConsole

AMD64

RU

{D5467DEC-22C9-4CD9-B340-FCEC983BB458}

Console

x86

RU

{07D27466-C7CE-4E66-8D96-47050C039ABB}

ACS

AMD64

SV

{AF5B4A94-741C-41EA-B10F-1654105BE3AC}

Console

AMD64

SV

{048E6139-70A1-4ED3-B95C-EB506A2C5E3C}

WebConsole

AMD64

SV

{A2C17E86-C2E8-4B60-857C-1EDA2D6E5187}

Console

x86

SV

{F4EDDEB1-E9CC-48CC-ABB7-5AEA5F5435F5}

ACS

AMD64

TR

{424AFB64-1437-47FF-A42B-A594614F946F}

Console

AMD64

TR

{E0C6FA88-5A94-4A1B-A7D0-457ED03B2428}

WebConsole

AMD64

TR

{BCA204D0-D12F-4F50-85BA-108FD1335E7B}

Console

x86

TR

{A50BF14A-7A27-4753-88C3-576FB24CCF9F}

ACS

AMD64

TW

{39A3BBB4-73F8-41B8-B56F-F0CA4CF4DCC6}

Console

AMD64

TW

{839F28D4-5B18-4C41-B835-DE4E54E2D8B2}

WebConsole

AMD64

TW

{EB0DEE21-6347-43A9-A2E6-F3818A5B6D38}

Console

x86

TW

{FB70EEE7-0CE7-4306-BC89-3C569D64F134}

ACS

AMD64

ZH-HK

{48E30733-0595-4881-AD87-476F4D7DB791}

Console

AMD64

ZH-HK

{949AA7A3-78B6-4B62-A94F-EFE9F70758A6}

WebConsole

AMD64

ZH-HK

{2162B6F1-FA6E-4C20-A295-B78BCF738D59}

Console

x86

ZH-HK



The RTMProductCodeGuid placeholder represents one of the following GUIDs:

Component

RTMProductCodeGuid

Server

{8070C91C-7D7C-4DAD-88B1-0966EEA9A8FE}

Console (AMD64)

{5142AB0B-73E3-4AD3-9D0F-65B3D9026769}

Console (x86)

{358C8AF0-25BB-425A-A4E6-7ADE54ED4736}

WebConsole (AMD64)

{5ED945BA-2BDD-4567-804E-8D3D2DB5CC9B}

ACS

{3E7464F7-A468-44E1-9A95-58349E022EAE}

Agent (AMD64)

{8B21425D-02F3-4B80-88CE-8F79B320D330}

Agent (x86)

{387306D9-78CE-4E0E-B952-28A50CC8B3EE}

Agent (IA-64)

{F3DDB021-89BC-464F-9107-69E2547D08FD}

Gateway

{80C2A57A-4193-4800-AA27-CD79553FE9DF}

SCX-ACS (AMD64)

{B30F4F71-2AF3-4542-855B-E1C7A31AC9A5}

SCX-ACS (x86)

{B30F4F71-2AF3-4542-855B-E1C7A31AC9A5}



File name

File size

Version

MomConnector.dll

683 KB

7.0.9538.1123

MOMModules.dll

2.49 MB

7.0.9538.1123

Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll

230 KB

7.0.9538.1123

Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll

1.05 MB

7.0.9538.1123

Microsoft.SystemCenter.Visualization.Component.Library.mpb

284 KB

7.0.9538.1123

Microsoft.Linux.RHEL.7.mpb

15,716 KB

7.4.4348.0



Need more help?

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

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×