Applies ToMicrosoft System Center 2012 Operations Manager Service Pack 1

Introduction

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

Issues that are fixed in this update rollup

Operations Manager

  • The Reset the baseline, Pause the baseline, and Resume the baseline actions fail when you run them against an optimized performance collection rule.

  • The DeltaSynchronizationengine work item times out on SQL operations, and Event ID 29181 is generated.

  • Running the Export-SCOMEffectiveMonitoringConfiguration cmdlet fails, and you receive the following error message:

    Subquery returned more than 1 value.

  • Time zone settings are not added to subscriptions when non-English display languages are set.

  • The Operations Manager dashboard experiences a performance issue that is caused by the TopNEntitiesByPerfGet stored procedure.

Known issues with this update

  • After you install this update rollup package on all roles on the server that is running System Center Operations Manager 2012 Service Pack 1 (except on the Agent and Gateway roles), the updates do not appear in the Add or Remove Programs item in Control Panel.

  • After you apply Update Rollup 6, you have to reopen the Operations Manager console in order to apply the Alert Attachment Management Pack fix.

  • After you install this update rollup package, the version number of the console is not changed.

  • If the ACS update package is installed, uninstalled, and then re-installed, the database upgrade script that is included in this update will not run. This behavior occurs because the database version is changed during the first installation of the ACS update. This could result in a server crash if the user reuses a partition with the partition still in place.The partition can be closed manually by going to the ACS database in Microsoft SQL Server Studio and then running the following script in a Query Editor window:

    begin tran -- mark all active partitions for closing if (select count(*) from dtPartition where Status = 0) > 0     update dtPartition set Status = 1 where Status = 0 commit tran

    In order to create a new partition, stop the AdtServer service, run the script, and then restart the AdtServer service.

  • After you install this update rollup package on a web console, you may receive the following error message in Internet Explorer:

    Server Error in '/OperationsManager' Application. To resolve this issue, close and then restart Internet Explorer.

  • When you try to import Microsoft.SystemCenter.Visualization.Component.Library, the import fails because of missing dependencies.To resolve this issue, import Microsoft.SystemCenter.Visualization.Component.Library again.

How to obtain and install Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1

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 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 packages that you want to install, and then click OK.

  6. Click Install updates to install the selected update packages.

Manual download of the update packages

Go to the following website to manually download the update packages from the Microsoft Update Catalog:

Download Download the Operations Manager Service Pack 1 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 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 WarehouseDWORD Name: Bulk Insert Command Timeout SecondsValue data:nnNote The placeholder nn is a value in seconds. For example, set the value data to 40 for a 40-second time-out.

Installation instructions

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/Tieringfeature.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.mpbNote This pack has the following dependencies:

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

      • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which 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

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

Uninstall information

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.

Patch name

Patch GUID

ENU

KB2965420-AMD64-Agent.msp

{1F52ADD1-50E7-46DF-9F9A-C5BB5F51B485}

KB2965420-AMD64-ENU-ACS.msp

{1726E977-0497-4462-AEEB-77507AB4BE2E}

KB2965420-AMD64-ENU-Console.msp

{4916C457-2741-424A-9F10-04BF643D42D9}

KB2965420-AMD64-ENU-WebConsole.msp

{637E9BE2-23E1-4209-8C08-E2E3BD60E6B7}

KB2965420-AMD64-Gateway.msp

{DE658C95-6CD8-45DE-ADE3-E262373A87F3}

KB2965420-AMD64-Server.msp

{0F39F268-3605-417C-BE66-587B08D63104}

CN

KB2965420-AMD64-CHS-ACS.msp

{54B8D63E-30FF-4F9A-B851-9219ECF65F22}

KB2965420-AMD64-CHS-Console.msp

{C1623DEE-6F37-40DB-A7FD-E60A3086584A}

KB2965420-AMD64-CHS-WebConsole.msp

{13A24D0B-381B-41C5-94A2-EEA44D3D147E}

KB2965420-i386-CHS-Console.msp

{7D6582DC-72DA-43B4-A598-281E21CDB716}

CS

KB2965420-AMD64-CSY-ACS.msp

{287142A8-4BAC-4EDF-850F-1E92FBD05A89}

KB2965420-AMD64-CSY-Console.msp

{3F52EAB0-3850-4574-91CD-A30BF12AA34D}

KB2965420-AMD64-CSY-WebConsole.msp

{95D01CFF-0253-478C-B2AD-7851108DC8B8}

KB2965420-i386-CHS-Console.msp

{5A0CD220-2177-4B79-8E78-3948697514B9}

DE

KB2965420-AMD64-DEU-ACS.msp

{79223C94-FD27-4C85-8915-8D8498C84175}

KB2965420-AMD64-DEU-Console.msp

{5BBC2014-C9B2-4B54-B621-40BF5D117696}

KB2965420-AMD64-DEU-WebConsole.msp

{F94DB4AF-F940-47A4-A65D-5D1946DBC7B3}

KB2965420-i386-DEU-Console.msp

{7DD34905-A003-4E88-942C-6B39EB23D518}

ES

KB2965420-AMD64-ESN-ACS.msp

{C4C33A66-4942-4695-8618-77A39E95CECE}

KB2965420-AMD64-ESN-Console.msp

{764E05E5-E9DE-4544-BDAF-3D474101CC2E}

KB2965420-AMD64-ESN-WebConsole.msp

{C3992315-5E01-4E9E-AEA6-1FE89A8930A8}

KB2965420-i386-ESN-Console.msp

{DCC06053-4D74-4564-B53F-6B27B877D4F7}

FR

KB2965420-AMD64-FRA-ACS.msp

{65325D72-BCB5-4323-9E3F-29727E1C47CB}

KB2965420-AMD64-FRA-Console.msp

{719B251A-08B0-482B-BF02-3DC33621C75D}

KB2965420-AMD64-FRA-WebConsole.msp

{79398F4D-809A-4E37-BCEF-FFF2C23C95A4}

KB2965420-i386-CHS-Console.msp

{63AFFD9C-3427-4008-AA19-BFE42AA7ED81}

HU

KB2965420-AMD64-HUN-ACS.msp

{23EC1D21-A1DC-4FB0-B6F2-AF3ED30254F4}

KB2965420-AMD64-HUN-Console.msp

{43F652A0-45F9-4793-8823-EAD8F843902E}

KB2965420-AMD64-HUN-WebConsole.msp

{32DDCA52-1935-4571-95A3-6C868F6C83D5}

KB2965420-i386-HUN-Console.msp

{63F5E021-F6D2-438B-A217-11BB4C19F951}

IT

KB2965420-AMD64-ITA-ACS.msp

{1F09AFF4-605C-497A-9205-163978437C8F}

KB2965420-AMD64-ITA-Console.msp

{E7072167-5EB5-4EF6-B921-CB99CC67A11C}

KB2965420-AMD64-ITA-WebConsole.msp

{AE5CE0A8-4A7B-4485-83F8-51224E37CC9E}

KB2965420-i386-ITA-Console.msp

{912C1A7B-F6F0-4511-A8DD-E47E9209CA9C}

JA

KB2965420-AMD64-JPN-ACS.msp

{FA381E21-1538-4B1B-9992-7B98CFF6660D}

KB2965420-AMD64-JPN-Console.msp

{C79B83FB-4B7A-4AAB-BE78-6822916B5BA2}

KB2965420-AMD64-JPN-WebConsole.msp

{746D2EC2-3245-4582-9627-2E1EB07CD2AF}

KB2965420-i386-JPN-Console.msp

{34970887-2A69-4A26-BCBC-21CC75D94EBD}

KO

KB2965420-AMD64-KOR-ACS.msp

{76E5729D-7124-4217-A4BE-F2340EE2A076}

KB2965420-AMD64-KOR-Console.msp

{B5E4A7CE-5217-43AF-9310-E0D1EB42F899}

KB2965420-AMD64-KOR-WebConsole.msp

{057B29F3-AFC6-40D5-9978-15FE679E8716}

KB2965420-i386-KOR-Console.msp

{86882475-70E2-48EA-AC22-65BE6958CE76}

NL

KB2965420-AMD64-NLD-ACS.msp

{85053F32-82E4-47F4-BE1F-9C8659E68634}

KB2965420-AMD64-NLD-Console.msp

{57D26FCD-1747-41E7-A14E-5D7862E649B8}

KB2965420-AMD64-NLD-WebConsole.msp

{5E18EEFD-D980-420C-992E-E422978FD89F}

KB2965420-i386-NLD-Console.msp

{245AB538-25A7-414C-AD8B-234A293EE47A}

PL

KB2965420-AMD64-PLK-ACS.msp

{F0A5B81A-8636-4CE9-B64D-921F2221E23D}

KB2965420-AMD64-PLK-Console.msp

{4FA247E4-84B2-48EC-8806-352C7C853010}

KB2965420-AMD64-PLK-WebConsole.msp

{5F2DA2B6-99B0-47E0-9916-175F41C4F3B3}

KB2965420-i386-PLK-Console.msp

{1679C30E-1387-446E-8315-57E6E3F16876}

PT-BR

KB2965420-AMD64-PTB-ACS.msp

{A504F5E8-CDA9-44CE-915C-97FF631645FA}

KB2965420-AMD64-PTB-Console.msp

{EA4E568D-AC11-45CA-9079-58278CFE1AFC}

KB2965420-AMD64-PTB-WebConsole.msp

{79596423-2EC9-43B2-AD45-AE08AE0ADA63}

KB2965420-i386-PTB-Console.msp

{479780A1-C4CC-4B13-B46D-D00F76EC394C}

PT-PT

KB2965420-AMD64-PTG-ACS.msp

{21B33DF4-E4DE-456A-A565-3E1B49F2F402}

KB2965420-AMD64-PTG-Console.msp

{F567E814-5C26-4982-9F90-9EF4094E34E2}

KB2965420-AMD64-PTG-WebConsole.msp

{EEBA37AB-EE8B-4ABC-8458-2EC27CCFD8EB}

KB2965420-i386-PTG-Console.msp

{700AC711-027A-4B01-9502-DD5C3137BD8D}

RU

KB2965420-AMD64-RUS-ACS.msp

{55D56E40-05A7-42B7-820D-495D9EEEFD16}

KB2965420-AMD64-RUS-Console.msp

{2EA3431B-C319-4170-BB87-09ED636327B0}

KB2965420-AMD64-RUS-WebConsole.msp

{82B9FC41-85EE-46EF-ABE2-26CFA0E7DE7D}

KB2965420-i386-RUS-Console.msp

{939278FF-000F-4481-8FE9-6B3B3F722609}

SV

KB2965420-AMD64-SVE-ACS.msp

{2E3C2304-AFF4-4D19-963E-FEBA5239478F}

KB2965420-AMD64-SVE-Console.msp

{51C2342E-DD87-4B35-8FF9-5254410AEC0D}

KB2965420-AMD64-SVE-WebConsole.msp

{E4431DDA-95EB-4AD2-A29F-E356FBB5D4C5}

KB2965420-i386-SVE-Console.msp

{F3959A1B-9BA1-42CC-AAC0-6F29ABC96212}

TR

KB2965420-AMD64-TRK-ACS.msp

{5BBA1CBC-A89F-43D2-A735-0142A4C78B5C}

KB2965420-AMD64-TRK-Console.msp

{F4E2B9A0-4129-4864-BBBF-BB65CB402A54}

KB2965420-AMD64-TRK-WebConsole.msp

{80390856-9CCD-4FD5-B76F-6FE901E86063}

KB2965420-i386-TRK-Console.msp

{2A5C60E7-8A95-4BE8-B8DF-F4151CA38A6D}

TW

KB2965420-AMD64-CHT-ACS.msp

{78529104-3056-4B6E-B7B7-E82E2282FA6B}

KB2965420-AMD64-CHT-Console.msp

{38378BBC-3BA3-44E0-AB7F-324C2AA157CD}

KB2965420-AMD64-CHT-WebConsole.msp

{31EEDB05-B808-4ACF-947A-A4749CA987F2}

KB2965420-i386-CHT-Console.msp

{F180763A-61B5-4A73-BBBB-CC890A52C8BE}

ZH-HK

KB2965420-AMD64-ZHH-ACS.msp

{AF0BE6FD-C404-4956-8565-3EB0FAC29871}

KB2965420-AMD64-ZHH-Console.msp

{3F2BDC0F-D46C-465F-AC65-0F6D226C2AE9}

KB2965420-AMD64-ZHH-WebConsole.msp

{271A9F11-E460-408F-98D7-33BD4C62FF1C}

KB2965420-i386-ZHH-Console.msp

{4567F4DE-C893-4492-8151-D204E5A62799}

Files that are changed

File size

File version

update_rollup_mom_db.sql

Not applicable

Not applicable

HealthService.dll

3.15MB

7.0.9538.1117

HealthServiceMessages.dll

1.29MB

7.0.9538.1117

AgentConfigManager.dll

127KB

7.0.9538.1117

Microsoft.Mom.Common.dll

254KB

7.0.9538.1117

csdal.dll

86.7KB

7.0.9538.1117

Microsoft.Mom.UI.Components.dll

5.85MB

7.0.9538.1117

UR_Datawarehouse.sql

Not applicable

Not applicable

Microsoft.SystemCenter.Visualization.Library.mpb

Not applicable

Not applicable

Microsoft.SystemCenter.GTM.Tool.Widgets.dll

Not applicable

7.0.9538.1117

Microsoft.EnterpriseManagement.Presentation.Controls.dll

1.69MB

7.0.9538.1117

Microsoft.EnterpriseManagement.Presentation.Controls.dll (Silverlight)

1.69MB

7.0.9538.1117

Microsoft.EnterpriseManagement.Monitoring.Components.dll

1.8MB

7.0.9538.1117

Microsoft.EnterpriseManagement.Monitoring.Components.dll(Silverlight)

1.8MB

7.0.9538.1117

Microsoft.SystemCenter.Visualization.Component.Library.mpb

Not applicable

Not applicable

Microsoft.EnterpriseManagement.DataAccessService.OperationsManager.dll

1.08MB

7.0.9538.1117

Microsoft.EnterpriseManagement.DataAccessLayer.dll

2.38MB

7.5.2905.166

Microsoft.EnterpriseManagement.RuntimeService.dll

386KB

7.0.9538.1117

Microsoft.EnterpriseManagement.Utility.WorkflowExpansion.dll

70.7KB

7.0.9538.1117

Facebook LinkedIn Email
SUBSCRIBE RSS FEEDS

Need more help?

Want more options?

Discover Community

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders