Applies ToSystem Center 2012 R2 System Center 2012 R2 Operations Manager

Introduction

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

Issues that are fixed in this update rollup

Operations Manager

  • The "Remove-DisabledClassInstance" Windows PowerShell command times out without completingThe cmdlet takes lots of time to complete in large SCOM installations and sometimes times out without completing its work. This is fixed by optimizing the query that is used for deletion. 

  • Duplicate closed alertsThe Find option in a message view sometimes gives results of the current search together with the results from previous searches. This occurs because of an update issue in the grid and is fixed so that values are displayed that correspond only to the current search. 

  • Topology widget objects lose location when they are opened in a console that has a different locale and decimal formatTopology widgets that are created in one locale but are viewed from another locale display an incorrect location because of the widget's inability to interpret locale-specific formatting. This issue is fixed, and users can now create and view topology widgets from different locales.

  • WebConsole Details widget does not display anythingWhen you click a message in the Alert widget, the details of the message are not displayed in the details widget on WebConsole. This issue is fixed by fixing the XAML page of the details widget. The XAML page was preventing the data from being displayed on the page.

  • Top 10 Performance widgets (WebConsole) are sometimes emptyThe Top 10 Performance widgets (WebConsole) are sometimes empty because of a performance issue. This issue was fixed in Update Rollup 3 through an MPB file that requires a manual import. Because many users missed importing the MPB, a fix is included in this update rollup as an SQL query update.

  • Problem with decoding SCOM trace log filesSometimes Operations Manager trace logs do not decode but generate the error "Unknown(X ): GUID=XXX (No Format Information found)." This occurs because the latest TMF files that contain formatting information for the related traces are missing. All TMF files are updated to make sure that traces are formatted correctly.

Unix/Linux Management Pack

  • JEE: WebLogic 12.1.3 servers on Linux or Solaris are not discoveredWebLogic 12cR1 Rel3 Java Application Servers that are installed on Linux and Solaris are not discovered.Note The UNIX or Linux agent must be updated after you install the Management Pack update to resolve this issue.Relevant log messages:/var/opt/microsoft/scx/scx.log

    2015-02-04T15:28:18,797ZTrace [scx.core.common.pal.system.appserver.appserverenumeration:379:15739:139715041470400] Weblogic process does not contain the 'platform.home' or 'weblogic.system.BootIdentityFile' commandline argument.2015-02-04T15:28:18,797ZTrace [scx.core.common.pal.system.appserver.appserverenumeration:462:15739:139715041470400] Merging previously known instances with current running processes

  • In rare cases, lots of omiagent processes may be observed on a UNIX or Linux computerIf a single instance of data that is returned by an OMI provider is larger than 64 kilobytes (KB), the omiagent process becomes unresponsive, and additional omiagent processes are created. This issue can occur on a managed UNIX- or Linux-based computer if a rule or monitor returns an instance of data larger than 64 KB. This is most likely to be seen when a custom shell command or script rules return lots of data in StdOut.Note After you upgrade the Operations Manager UNIX/Linux agent to the version that is contained in this Management Pack update, an instance that exceeds 64 KB will be truncated and will generate the following message in the scx.log file. You can use the log message to identify and change the workflow that is returning too much data.

    ExecuteCommand: Exceeded maximum output size for provider (64k), output truncated. Monitoring will not be reliable! Command executed: "

  • The SSLv3 protocol cannot be disabled in OpenSSL as used by the UNIX and Linux agentsWith this update, you can now disable the SSLv3 protocol for the Operations Manager UNIX and Linux agents. You can do this by adding a property to omiserver.conf (/etc/opt/microsoft/scx/conf). If SSLv3 is disabled, the UNIX and Linux agent will reject connections that cannot be negotiated by using TLS encryption. If SSLv3 is enabled (this is the default configuration), SSLv3 will be used only if TLS encryption cannot be negotiated.omiserver.conf options for configuration SSLv3

    Property

    Description

    NoSSLv3=true|false

    Enable/Disables use of SSLv3

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

Download information

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

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:

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 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 that 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 WarehouseDWORD name: Bulk Insert Command Time Out SecondsDWORD Value: 40Note 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.sqlNote 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:

    Update_rollup_mom_db.sql

  5. Import the following management packs:

    • Microsoft.SystemCenter.TFSWISynchronization.mpb. This has the following dependency:

      • Microsoft.SystemCenter.AlertAttachment.mpb. This 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

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

PatchCodeGUID

Component

Architecture

Language

{D39DF100-8CA1-4ADC-A06C-B0A2135CFEE9}

Agent

amd64

en

{57A107E8-D3BE-4C88-9C33-B386D59B4D2E}

ACS

amd64

en

{089800AE-8307-4236-A7FF-659619CBE84D}

Console

amd64

en

{AA95F6F7-419C-4589-BE22-B24C5C617ED1}

Reporting

amd64

en

{258976C7-50D0-4F71-A4EC-BBCAFEE105C2}

WebConsole

amd64

en

{B63EEEE5-C2E2-45D7-8B51-7332161BFB31}

Gateway

amd64

en

{08C61BC5-1D64-4B02-9770-E94286C5651C}

Server

amd64

en

{B3EAD815-13DD-4C8F-82FC-2C1DA8234DEB}

Agent

x86

en

{2CE4777F-C943-4B9A-B818-A7CEC0DBB438}

Console

x86

en

{8893192C-70B4-4CEE-9771-E1F1DB16BC9F}

ACS

amd64

cn

{C90C3324-0DE0-4540-96C0-49ABE1C8033E}

Console

amd64

cn

{0C3F57F7-4D7D-4FE9-83C9-53D867172465}

Reporting

amd64

cn

{5E252A72-6E55-4C3B-99BB-9B143E69D055}

WebConsole

amd64

cn

{CB02EA83-A2E1-4FEA-B8A7-410D79DD5F82}

Console

x86

cn

{D094C4CA-2DCE-4ECC-A73E-A02C685BD9D4}

ACS

amd64

cs

{6FE7F4D0-0CD3-4EF8-96D3-BB829C4CA2A0}

Console

amd64

cs

{B5AFC46C-3B34-4D4C-81F0-752FE5F7686D}

Reporting

amd64

cs

{04A4C055-42E7-4DEE-92E1-708CEB8BB824}

WebConsole

amd64

cs

{13C034A8-7ABF-4030-9961-CAD013CDCB76}

Console

x86

cs

{95080C1C-A2F8-43EE-97FD-C237A820DF0C}

ACS

amd64

de

{F99FE55C-4F48-49C1-AC83-0B19F73EE9D2}

Console

amd64

de

{D29AD1F4-4DCE-46A9-BA30-DF4E3CAD92A8}

Reporting

amd64

de

{C0F787F8-71C8-4B08-8965-548DADCF5140}

WebConsole

amd64

de

{99C22893-0061-47BD-A501-C188F5C4B11C}

Console

x86

de

{B0E2001F-A8EC-415F-9698-86354C29F127}

ACS

amd64

es

{30475DEC-9936-4871-8DF7-2A0970A3D797}

Console

amd64

es

{920683B7-71A1-43B8-A924-CEE935AA92F0}

Reporting

amd64

es

{DA895E97-90DA-452D-856F-B5308EA7409B}

WebConsole

amd64

es

{428A913D-EA7D-494F-BF9D-19983E728B84}

Console

x86

es

{894F2B6E-B6C7-46E1-A1A2-F29E2527F661}

ACS

amd64

fr

{95D5B136-1257-4F20-9695-506E2771D23D}

Console

amd64

fr

{47784EC2-3651-445A-A05F-F18534DF3409}

Reporting

amd64

fr

{65DDCEBD-454F-4263-AE20-DA0FE89A5D5D}

WebConsole

amd64

fr

{84AD6505-EFA9-45A2-9979-8D2EDF145DD2}

Console

x86

fr

{91D1DDB5-DE58-4E4E-976C-5A7AE0E9954D}

ACS

amd64

hu

{FB8E0099-3DAC-42A5-992E-ADF4CFD91F26}

Console

amd64

hu

{EC39BCB0-8B88-472C-BB60-7F7411B5F8A5}

Reporting

amd64

hu

{9F916083-8D1F-4920-B814-CD7CF74D4D8A}

WebConsole

amd64

hu

{498118B3-0B6A-45BE-9AD1-6A89EF718CAD}

Console

x86

hu

{30595599-2A74-44F3-801D-ECF8AE9CB5D6}

ACS

amd64

it

{40DD0FD0-2F6F-4690-90D2-3B6C7F88A71E}

Console

amd64

it

{71FC7284-9AC8-4159-924B-ABA677CCD964}

Reporting

amd64

it

{1987F851-B880-4A1B-82B9-5CC846CC2CB3}

WebConsole

amd64

it

{65B9893E-F0FC-4D5D-90E6-5C666C352EF9}

Console

x86

it

{897AC87C-83AA-4B0B-959A-BD7E73AF25EA}

ACS

amd64

ja

{67D0084F-7D9F-40DC-BC09-BEC5291A227A}

Console

amd64

ja

{0BD96698-4783-438E-AE31-A86C3036DA03}

Reporting

amd64

ja

{75D525E9-CB07-4570-AE79-3BA0052CD093}

WebConsole

amd64

ja

{D7BB1B2B-2D9A-4FFD-A843-C8203445163C}

Console

x86

ja

{D45F0B3D-C948-4C00-93B1-730986D10DE7}

ACS

amd64

ko

{387B72A8-182A-4F76-9E40-A0F4F7E39B73}

Console

amd64

ko

{55A980FA-A775-488B-A3B5-47050EBA0C9B}

Reporting

amd64

ko

{AB4C3BFD-2D16-4510-9953-84887BB7A291}

WebConsole

amd64

ko

{9A160C3A-752C-497B-9788-AE467957B183}

Console

x86

ko

{CADEEB34-16ED-41D7-B365-C2A00BDC5475}

ACS

amd64

nl

{2218B45F-D683-48D4-9196-501B0A746622}

Console

amd64

nl

{7FDADF47-2906-4E48-B013-EE6D67B986A7}

Reporting

amd64

nl

{AFEED9D1-5001-4559-92CC-F9B9341C8F3D}

WebConsole

amd64

nl

{33CC8E55-FE1F-4FFE-BD16-2A989EF7D4C9}

Console

x86

nl

{6D8D72A0-0044-4F36-81C8-F04F8490D934}

ACS

amd64

pl

{7C3756E9-6671-42AC-BD80-ACAD52130642}

Console

amd64

pl

{1E4A55AF-0BEE-4456-92C9-957706AF3136}

Reporting

amd64

pl

{9AAC3C2C-9621-49F5-A851-AA823259DB2F}

WebConsole

amd64

pl

{9E5678FF-E677-4AE4-91A7-95AA919D1965}

Console

x86

pl

{5A3AFCA6-2D81-4A3E-A0CD-46DA39F32B6A}

ACS

amd64

pt-br

{DD9ED6CB-A96A-4417-A91A-A45EFD1C94D8}

Console

amd64

pt-br

{E8AB52C5-B393-4822-87D7-E6C297FE557D}

Reporting

amd64

pt-br

{3B0BF646-72AF-425B-AD5A-0EE5BCD0D6C3}

WebConsole

amd64

pt-br

{9747911C-FA55-4506-B80E-F489C2B05F92}

Console

x86

pt-br

{70D50123-ABAF-4FB1-8E22-060461DEFFD9}

ACS

amd64

pt-pt

{8F63D278-C0A8-411B-945F-236C2ED1197B}

Console

amd64

pt-pt

{5B173041-6352-4EB5-9287-B7E812C0B65A}

Reporting

amd64

pt-pt

{DA577D6E-DF29-4CC7-AED3-6E737A1B802D}

WebConsole

amd64

pt-pt

{F0FAA37C-4878-443F-BF92-22F7C9CF7A2C}

Console

x86

pt-pt

{C83A8EBA-5E15-4A9B-A3CA-A228B3A37296}

ACS

amd64

ru

{3846FF4A-065C-4C5E-AC7F-57ED0464A7CF}

Console

amd64

ru

{FD823368-A50A-44FE-8893-EDF773B5070E}

Reporting

amd64

ru

{CBC0F282-83CB-42EB-8C4A-96AD93AE2554}

WebConsole

amd64

ru

{50EBE322-E438-449C-B5C9-536054A86EE2}

Console

x86

ru

{102FFFCF-721A-4CF0-A216-8FF3D64F4418}

ACS

amd64

sv

{6D2556E1-8C00-4460-B026-FCA545CFFB5E}

Console

amd64

sv

{45CB944B-F502-4E33-B49A-FFC71A8223B5}

Reporting

amd64

sv

{6792C9B6-F0C5-4D1F-A170-0F065237EBAA}

WebConsole

amd64

sv

{3008AB1E-7171-4A61-9A30-9DC5410F9EA7}

Console

x86

sv

{682F3F36-0A49-4347-AA10-F3B7DE3809B6}

ACS

amd64

tr

{8CB2E13E-815A-45D7-A0B0-2DB668B89606}

Console

amd64

tr

{A9BDDF62-6388-49F9-ABE3-DEC490980EFB}

Reporting

amd64

tr

{20EFD135-1ED2-4DCB-B505-A22A15490439}

WebConsole

amd64

tr

{10C0AF6B-C776-4A9F-BB09-809BCF9260BF}

Console

x86

tr

{89C82DA0-E9DB-4E9A-84FE-2431D1B7E4E6}

ACS

amd64

tw

{DBD2F943-1279-46B9-8629-75073E7FB07A}

Console

amd64

tw

{BE58D998-8EA5-453B-90D0-064A71391CE2}

Reporting

amd64

tw

{28637205-3BC2-483F-9FC9-CBE73DB22C90}

WebConsole

amd64

tw

{7837DFBA-FA6F-4CC5-B5E3-F72C82B226EF}

Console

x86

tw

{9126DCC0-E65A-47AD-A359-48C2E5780555}

ACS

amd64

zh-hk

{887270B9-A2C0-45DF-8705-0CBF551A88C0}

Console

amd64

zh-hk

{54F724AF-F657-4C98-ABC6-1EFB639B04EC}

Reporting

amd64

zh-hk

{9B14FC4A-5A30-4090-A6A9-A867145DE643}

WebConsole

amd64

zh-hk

{B714AEB1-E6BB-488F-9339-DDD095FC0845}

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 changed in this update rollup. If you do not have all previous update rollups installed, files other than those that are 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

Microsoft.EnterpriseManagement.DataAccessLayer.QueryCache.dll

7.5.3079.354

2.14 MB

Microsoft.EnterpriseManagement.DataAccessLayer.dll

7.5.3079.354

2.40 MB

Microsoft.Mom.UI.Components.dll

7.1.10226.1064

5.87 MB

Microsoft.EnterpriseManagement.UI.Authoring.dll

7.1.10226.1064

9.44 MB

Microsoft.Mom.UI.common.dll

7.1.10226.1064

2.19 MB

Microsoft.EnterpriseManagement.Presentation.Controls.dll

7.1.10226.1064

1.70 MB

monitoringportal.xap

7.1.10226.1064

3.92 MB

update_rollup_mom_db.sql

7.1.10226.1064

90.4 KB

UR_DataWarehouse.sql

7.1.10226.1064

111 KB

MonAgentTraceTMF.CAB

7.1.10226.1064

1.64 MB

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