Update Rollup 13 for System Center 2012 R2 Operations Manager

Applies to: System Center 2012 R2 Operations Manager

Introduction


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

Issues that are fixed


  • When there are thousands of groups in a System Center Operations Manager environment, the cmdlet Get-SCOMGroup -DisplayName "group_name" fails, and you receive the following message:

    The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.
  • When you run System Center 2012 R2 Operations Manager in an all-French locale (FRA) environment, the Date column in the Custom Event report appears blank.

  • The Enable deep monitoring using HTTP task in the System Center Operations Manager console does not enable WebSphere deep monitoring on Linux systems.

  • When overriding multiple properties on rules that are created by the Azure Management Pack, duplicate override names are created. This issue causes overrides to be lost.

  • After you install Update Rollup 11 for System Center 2012 R2 Operations Manager, you cannot access the views and dashboards that are created on the My Workspace tab.

  • When the heartbeat failure monitor is triggered, a "Computer Not Reachable" message is displayed even when the computer is not down.

  • The Get-SCOMOverrideResult PowerShell cmdlet does not return the correct list of effective overrides.

  • When creating a management pack (MP) on a client that contains a Service Level (SLA) dashboard and Service Level Objects (SLO), the localized names of objects are not displayed properly if the client's CurrentCulture settings do not match the CurrentUICulture settings. In the case where the localized settings are English English, ENG, or Australian English, ENA, there is an issue when the objects are renamed.

  • This update adds support for OpenSSL1.0.x on AIX computers. With this change, System Center Operations Manager uses OpenSSL 1.0.x as the default minimum version supported on AIX,  and OpenSSL 0.9.x is no longer supported.

How to obtain Update Rollup 13 for System Center 2012 R2 Operations Manager


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

If your computer is running Windows Server 2016 or a later version of the operating system, follow these steps:

  1. Click Start, and then click Settings.
  2. In Settings, click Updates & Security.
  3. On the Windows Update tab, 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

Go to the following websites to manually download the update packages from the Microsoft Download Center:

 Download the Operations Manager update package now.

For information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Installation instructions for Operations Manager


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 don't 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.

  • Install this update rollup package within a few hours after you install the System Center 2012 R2 Operations Manager server.

  • 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:

    <machineKeyvalidationKey="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 that's 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.

    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

    322756 - How to back up and restore the registry in Windows

    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 settings:

    Registry location: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft OperationsManager\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.

  • Reports for Downtime duration do not take business hours into consideration. Business hours are being calculated even when the Business hours check box is cleared. These updated RDL files resolve the issue.

    Note The updated RDL files are located on an updated Management Server 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.aspx.
    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.

Supported installation 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
    • Reporting
    • Agent

  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 following Database SQL script on the Datawarehouse server against the OperationsManagerDW database:
     
    UR_Datawarehouse.sql

    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. Run the following database SQL script on the Database server against the OperationsManager database:
     
    Update_rollup_mom_db.sql
  5. Import the following management packs:
    • Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependencies:
      • 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 dependencies:
      • Microsoft.SystemCenter.Apm.Infrastructure.mpb
      • Microsoft.SystemCenter.Apm.Library.mpb
    • Microsoft.SystemCenter.Apm.Library.Resources.(LANGUAGECODE_3LTR).mpb
    • Microsoft.Windows.InternetInformationServices.2016.mp (this MP has to be downloaded separately from the Microsoft Update Catalog) which has the following dependency:
      • Microsoft.Windows.Server.2016.Discovery.mp (this MP has to be downloaded separately from the Microsoft Update Catalog)
    • 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
    • Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp
    • Microsoft.SystemCenter.Visualization.ServiceLevelComponents.mpb

For information about how to import a management pack from a disk, see How to Import an Operations Manager Management Pack on the Microsoft TechNet website.

Note Management packs are included in the Server component updates in the following location:

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

UNIX and 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 13 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.

Uninstall information


To uninstall an update, run the following command:

msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid

Note The PatchCodeGuid placeholder represents one of the following GUIDs.

PatchCodeGUID

Component

Architecture

Language

{8592AC31-5338-47C6-B0B2-B8752EB8256D}

Agent

amd64

en

{6CA0267C-5C68-46DC-96AF-152A7C5C7220}

ACS

amd64

en

{D619588C-6D7C-4BEC-902F-13C1681AA02E}

Console

amd64

en

{D6D6EAD2-3EAD-4976-AEEC-E80B20862DCC}

Reporting

amd64

en

{9B15724B-02A8-4783-95AB-648F7B74F228}

WebConsole

amd64

en

{185DCAC9-125C-4EE0-BB53-2E105D67D635}

Gateway

amd64

en

{3975C30B-7B52-401B-AAFF-DD822C21D9CC}

Server

amd64

en

{D514F41F-CA8E-4A89-97A0-059ABC692AD4}

Agent

x86

en

{B76A62B4-4142-4DED-A8EA-BA18BDB1BE41}

Console

x86

en

{40836C84-E061-4E3F-9B6F-D633FED02411}

ACS

amd64

cn

{6E4224E5-7D07-4C6F-86A5-BA80D7F5BB7F}

Console

amd64

cn

{76CC38F7-7222-48E1-B9A1-93313C7483A7}

Reporting

amd64

cn

{7A65D7ED-BC64-42EF-ADF4-AE762EB7B816}

WebConsole

amd64

cn

{802DBCFB-20F9-4E39-8956-094F9B917386}

Console

x86

cn

{01D7355C-1229-40C0-A71C-4ED73A520EBA}

ACS

amd64

cs

{6810C7B3-A9B3-4E3B-A1CD-8E4C349062F3}

Console

amd64

cs

{4032B22E-62EE-4632-8CDB-2873CBA446F3}

Reporting

amd64

cs

{913D4771-8408-4461-81BC-9855B7DD3B23}

WebConsole

amd64

cs

{DB96E613-25D6-49CC-84BB-565C3367CFED}

Console

x86

cs

{17FA6B7B-8D92-433C-9BBC-487296F0EA0C}

ACS

amd64

de

{D45E040C-864D-4F33-8A93-229753402833}

Console

amd64

de

{ADA28E9A-FEA2-424C-AC48-8646872AF8A0}

Reporting

amd64

de

{8C453BDD-A2BB-4F9C-9A8D-3BBECAA52BA0}

WebConsole

amd64

de

{7F75DD66-22EE-4899-8610-26866ACAD1B2}

Console

x86

de

{0E863817-913F-4AE4-9F69-EAB1E95DFA81}

ACS

amd64

es

{5F1D0961-ABB2-48FE-905C-7072AA6DEB10}

Console

amd64

es

{F674411F-A18F-47E1-B4FE-06BB4653F1FE}

Reporting

amd64

es

{3A45AA76-5A31-4179-9E04-90E0C79E52ED}

WebConsole

amd64

es

{AAB8CEA7-0336-4C35-8589-48E8116EDFD3}

Console

x86

es

{12FE313C-900D-4E61-809A-72B7AC410805}

ACS

amd64

fr

{3CE279EB-0C12-44F0-96DD-13B782783880}

Console

amd64

fr

{EBB48450-27AF-41D2-9FD0-E0D25224868D}

Reporting

amd64

fr

{CE62F82B-0F6E-4846-8C6A-BCC128E3F6B3}

WebConsole

amd64

fr

{A32255ED-5C98-4575-A454-E57E454B4BC1}

Console

x86

fr

{65A08B79-5E52-4810-95D4-9600A7976ABC}

ACS

amd64

hu

{0DD32C70-B886-4EEF-967E-65ADC4DF39D2}

Console

amd64

hu

{2980706C-A63E-4F90-A2EC-B12B3929258A}

Reporting

amd64

hu

{1AFB72E3-2EA1-458C-AE1E-A256548DD14A}

WebConsole

amd64

hu

{CA56135C-3578-4BDB-93AE-CD4061F467F5}

Console

x86

hu

{CA44BF12-A184-4CEE-99BA-BF80328B0FBF}

ACS

amd64

it

{16579350-8D55-4D56-BB93-744B068D0DB7}

Console

amd64

it

{DE3DED20-FD2F-4CAB-A037-467203AD517B}

Reporting

amd64

it

{B7A05ABD-C064-4F92-9917-D0620A11F3F3}

WebConsole

amd64

it

{A11EF014-0BB2-402D-8767-43EE7553285C}

Console

x86

it

{3D99D7DA-3AFB-48CA-BF4C-E3110FB0D330}

ACS

amd64

ja

{1DE3D74A-024A-4B8E-ABFC-126D83DA7459}

Console

amd64

ja

{87BE700F-80B9-402A-BF0F-44924DE15037}

Reporting

amd64

ja

{6644E59D-1422-428E-A606-CB2BB072A53A}

WebConsole

amd64

ja

{A36193F2-3183-4177-A481-A2EEEC938FBC}

Console

x86

ja

{6929632D-2990-4FFA-808E-8373892E64F2}

ACS

amd64

ko

{A49BC793-B3A9-4885-9E29-649F98F900A2}

Console

amd64

ko

{8C58D2BE-AB97-432D-8B87-B9DB7865CA77}

Reporting

amd64

ko

{8C7F7BEA-644A-45B5-A1F2-1DCA1781AC59}

WebConsole

amd64

ko

{5BCE64BD-40B9-4B07-A7B4-E0FC091737C5}

Console

x86

ko

{4C27EF6A-6B30-4857-B151-1DD9E3462080}

ACS

amd64

nl

{6BA29F7D-7120-48A5-B6C8-F8E5D2E1CA6C}

Console

amd64

nl

{16536909-4F31-4085-8BF9-8876BC8341BF}

Reporting

amd64

nl

{7797A01D-E26C-4A13-9463-C3DF663F64DC}

WebConsole

amd64

nl

{B0FF08CD-A343-4173-960C-568A04D8424B}

Console

x86

nl

{43561443-8C75-4BDB-B264-6A006F6A0CB0}

ACS

amd64

pl

{0C8D05E3-69DF-4C88-8572-33CEB8F39D68}

Console

amd64

pl

{A445DCAF-802A-4F45-B540-FB9E405B36B2}

Reporting

amd64

pl

{CF1B8E08-73D9-4967-A8D6-A165F553BFE8}

WebConsole

amd64

pl

{240A93B5-92BC-4A9B-9C3F-62ADEFD698EC}

Console

x86

pl

{A7FAB9FB-0346-4A62-8392-AC75C2856139}

ACS

amd64

pt-br

{EF42F747-BE36-41DC-B54F-36A713A02372}

Console

amd64

pt-br

{CFC135EF-C516-44C1-B405-D88767CCE454}

Reporting

amd64

pt-br

{9E1262D8-7D06-412A-8ECB-0BD26CF2CD87}

WebConsole

amd64

pt-br

{52EBFC91-BB30-43AB-8B4F-0D4043387A45}

Console

x86

pt-br

{3DECA94A-4008-4C4C-85BE-BB1E1CEDDC5F}

ACS

amd64

pt-pt

{3721B5BF-2E18-4360-B8A9-FEE374FFC9BB}

Console

amd64

pt-pt

{88F05F48-36A2-45C0-A311-984CDC4B27DB}

Reporting

amd64

pt-pt

{BBDFE8B3-05A0-4446-ADEF-9F1F31CC3973}

WebConsole

amd64

pt-pt

{7E15C449-F0BB-437E-B333-68498925A392}

Console

x86

pt-pt

{D7C3FB66-F099-4EA8-81EB-3E4746D6E9CB}

ACS

amd64

ru

{D6A0B0A4-FEE7-4737-921B-A10D3A38E000}

Console

amd64

ru

{68555626-1B1E-4B4E-9F31-11FF0F52460D}

Reporting

amd64

ru

{C2FA8B1C-0552-4ABA-A207-4B5CB6DC9A99}

WebConsole

amd64

ru

{8756E05A-4527-4B69-827F-80796BC3C223}

Console

x86

ru

{A029CB12-C91B-4B9B-B303-2CAA4671EF06}

ACS

amd64

sv

{8AB2E870-A012-43FE-8783-4E6A636A4368}

Console

amd64

sv

{B475D836-4C99-408E-B5EB-07271DE917AF}

Reporting

amd64

sv

{6420FDD3-9AE9-4532-BFB0-B1EDDAE77A20}

WebConsole

amd64

sv

{DD49FF91-68B0-4BF5-9EA7-0F0C349D4DB0}

Console

x86

sv

{7FF5CB6E-C536-492D-8A9F-61366B172A9B}

ACS

amd64

tr

{EDCED9E2-5BA9-4092-843C-90F049BB3E79}

Console

amd64

tr

{93FDDE1B-8A7C-4768-AED6-EDEBD6A418DE}

Reporting

amd64

tr

{D2BFF97D-36E3-4ACF-B8CF-F6204E554947}

WebConsole

amd64

tr

{50356596-0251-4913-BEDA-797A9A150F2D}

Console

x86

tr

{1FE89FCD-B266-4589-8D72-41B1D433AD53}

ACS

amd64

tw

{6C7ECAD0-6248-4043-8A23-BCA8AC09C4AF}

Console

amd64

tw

{B583C7FA-6A91-4B29-AC39-3AA64A74DA3A}

Reporting

amd64

tw

{8173BADD-C7BA-4D4D-B9F7-211C1F8E7A15}

WebConsole

amd64

tw

{48A2DE55-1C40-45A7-9B9D-F98F31760545}

Console

x86

tw

{716C9571-1907-42A4-9E66-F5A9495AE5C6}

ACS

amd64

zh-hk

{58BB3356-7C44-4141-8149-08A7ED028EEE}

Console

amd64

zh-hk

{EAE9F7A2-ADD3-43CD-9B08-E11EEF9B4AD2}

Reporting

amd64

zh-hk

{EA2B4305-030B-489D-9395-EB2EBA23F66D}

WebConsole

amd64

zh-hk

{CCCF23E4-93D3-4C99-B323-CD90CB325576}

Console

x86

zh-hk

Additionally, the RTMProductCodeGuid placeholder 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}

ACS

{8574A035-1191-4EBA-BA6C-1F4D37171CE2}

Agent (AMD64)

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

Agent (x86)

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

Reporting

{D6E655E7-6318-4C50-B184-55E70DB179C1}

Files updated in this update rollup