System Center 2012 Operations Manager SP1 Update Rollup 5

Operations Manager

Issue 1

An error occurs when you run the p_DataPurging stored procedure. This error occurs when the query processor runs out of internal resources and cannot produce a query plan.

Issue 2

By default, data warehouse bulk-insert commands use an unchangeable 30-second time-out value that may cause query time-outs.

Issue 3

Many 26319 errors are generated when you use the Operator role. This issue causes performance problems.

Issue 4

Diagram component does not publish location information in the component state.

Issue 5

Renaming a group works correctly on the console. However the group appears with the old name when you try to override a monitor or scope a view based on group.

Issue 6

SCOM synchronization is not supported in the localized versions of Team Foundation Server.

Issue 7

An SDK process deadlock causes the Exchange correlation engine to fail.

Operations Manager - UNIX and Linux Monitoring (Management Pack Update)

Issue 1

In rare cases, the agent on a Solaris Zone that is configured to use dynamic CPU allocation with Dynamic Resource Pools may hang during routine monitoring.

Note This issue can occur on any monitored Solaris Zone that is configured to use Dynamic Resource Pools and a "dedicated-cpu" configuration that involves a range of CPUs.

Issue 2

If the agent fails to retrieve process arguments from the getargs subroutine on an AIX-based computer, the monitored daemons may be incorrectly reported as offline. An error message that resembles the following is logged in the agent log:

.
Issue 3

The agent on AIX-based computers considers all file cache to be available memory and does not treat minperm cache as used memory. After this update rollup is installed, available memory on AIX-based computer is calculated as: free memory + (cache – minperm).

Issue 4

The Universal Linux agent fails to install on Linux computers with OpenSSL versions greater than 1.0.0 if the library file libssl.so.1.0.0 does not exist. An error message that resembles the following is logged:

Issue 5

Spurious errors that are related to the InstanceID property of the SCX_Endpoint are logged in the System log every four hours.

Installation instructions for Operations Manager

Known issues for this update

• After you install the update rollup package on all roles on the server that is running System Center Operations Manager 2012 (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 5, the Operations Manager console has to be reopened in order to apply the Alert Attachment Management Pack fix.

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

• If the ACS update package is installed, uninstalled then re-installed the database upgrade script that's included in this update will not run, because the database version is changed during the first installation of the ACS update. This could trigger a server crash if the user reuses a partition with the partition still in place. 
  
  The partition can be closed manually by using SQL Server Studio, navigating to the ACS database and 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 

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

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

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 language neutral, 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, 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.

• 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
  
  Note 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 Issue 2 (Data warehouse Bulk Insert Commands time-out issue) adds a registry key that can be used to set the time-out (in seconds) for the data warehouse bulk insert commands. These are the commands that insert new data into the data warehouse. The key name is:
  
  HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse\
  The value name is:
  
  Bulk Insert Command Timeout Seconds
  
  The value is a dword value. For example, the value name should be set to 40 for a 40 second time-out.

Supported installation order

We recommend that you install the update rollup package in the following order:

1. Install the update rollup package on the following server infrastructure:

   • Management server(s)

   • Gateway servers

   • ACS

   • Web console server role computers

   • Operations console role computers

2. Manually import the management packs.

3. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

Notes

• Install the update rollup package on agents either before or after you install the update rollup package on the server infrastructure.

• If the Connected MG/Tiering feature is enabled, first update the top tier of the Connected MG/Tiering feature.

• Update Rollup 5 files have a version of 9538.1106.

Installation information

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 http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2904680

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:

4. • UR_Datawarehouse.sql

   
   Note This script is located in the following path:
   
   %SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server \SQL Script for Update Rollups\.

5. Execute the following Database sql script on the Database server against the OperationsManagerDB database:
   
   o    Update_rollup_mom_db.sql

6. Import the following management packs:

   • Microsoft.SystemCenter.AlertAttachment.mpb

   • Microsoft.SystemCenter.IntelliTraceProfiling.mpb, which has the following dependencies:

     • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb
       
       Note Install this file from the System Center Operations Manager (SCOM) 2012 SP1 Media.

     • Microsoft.Windows.InternetInformatonServices.Common.mpb
       
       Note Install this file from the 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

   
   
   

For information about how to import a management pack from a disk, see the following Microsoft TechNet website:

How to Import an Operations Manager Management Pack

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 RTMProductCodeGuid

Note In this command, RTMProductCodeGuid is one of the following GUIDs:

Additionally, PatchCodeGuid is one of the following GUIDs:

Installation instructions for Operations Manager - UNIX and Linux Monitoring (Management Pack Update)

To 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 SP1– Operations Manager environment.

2. Download and the updated management packs for System Center 2012 from the following Microsoft website: 
   
   System Center Monitoring Pack for UNIX and Linux Operating Systems

3. Install the management pack update package to extract the management pack files.

4. Import the updated Microsoft.Unix.Library management pack (from the \2012 SP1\ folder), Microsoft.Unix.LogFile.Library management pack bundle, Microsoft.Unix.ShellCommand.Library management pack bundle, Microsoft.Unix.Process.Library management pack bundle, and the library management packs relevant to the Linux or UNIX platforms that you are monitoring in your environment.
   
   Note The Microsoft.Linux.Universal management packs are also in the \2012 SP1\ folder.

5. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment

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