Update Rollup 6 for SCOM 2012 R2 has just been released. As usual the update can be done through windows update or downloaded through the MS catalogue here. As always give this update a thorough test before deploying to your live environments.

Fixes in this update:

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,797Z
  Trace [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,797Z
  Trace [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

  Collapse this tableExpand this table

  Property	Description
  NoSSLv3=true|false	Enable/Disables use of SSLv3