Description of Update Rollup 4 for System Center 2012 Operations Manager Service Pack 1

Installation instructions for Operations Manager

Known issues with this update

• After you install the 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 4, 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 reinstalled, the database upgrade script that is included in this update will not run 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 when the partition still present.
  
  The partition can be closed manually in SQL Server Studio. To do this, browse to the ACS database, and then run 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 AdtServer, run this script, and then restart AdtServer.
• After you install the update rollup package on a web console, you may receive the following error message when you access ASP.NET webpages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0:
  
  
  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 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, 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"/>

Supported installation order

1. Install the update rollup package on the following server infrastructure:
   • Management server or servers
   • Gateway servers
   • Reporting servers
   • 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.

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

Installation information

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. Execute the UR_Datawarehouse.sql SQL script on Datawarehouse Server against the OperationsManagerDW database.
   
   Note This script is included in the server component update. After the installation is complete, you can fid the script in the following folder:
   %SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server \SQL Script for Update Rollups\
4. Import the following management packs:
   • Microsoft.SystemCenter.Apm.Infrastructure.mpb
   • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb
   • Microsoft.Windows.InternetInformationServices.CommonLibrary.mp
   • Microsoft.SystemCenter.Advisor.Internal.mpb
   • Microsoft.SystemCenter.AlertAttachment.mpb
   • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
   • 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.Image.Library.mp
   • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
   • Microsoft.SystemCenter.Visualization.Library.mpb
   Note Management packs are included in the server component updates in the following folder:
   
   %SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server\Management Packs for Update Rollups

Uninstall information

File information

Operations Manager Update (KB2880799)

How to install Operations Manager UNIX and Linux monitoring packs and agents

1. Apply Update Rollup 4 to your System Center Operations Manager 2012 Service Pack 1 environment.
2. Download the updated management packs 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 following updated management packs and management pack bundles:
   • 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
   • The library management packs that are 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.