Description of Update Rollup 9 for Microsoft System Center 2012 Operations Manager SP1

• 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. After you install the web console update, 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"/>
  To learn about how to add a line to the <system.web> section of the web.config file, see the "Workaround" section of 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 5 for System Center 2012 Operations Manager Service Pack 1 describes a registry key that the user can add to set the time-out (in seconds) for the data warehouse bulk insert commands. The following is the registry setting that controls the time-out value when new data is inserted into the data warehouse.
  
  
  Registry key:HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse
  DWORD Name: Bulk Insert Command Timeout Seconds
  Value data:nn
  
  Note The nn placeholder represents a value in seconds. For example, set the value data to 40 for a 40-second time-out.

1. Install the update rollup package on the following server infrastructure:
   • Management servers
   • Gateway servers
   • Web Console Server role computers
   • Operations Console role computers
2. Apply SQL scripts. (See the installation information for the update.)
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.

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. Select the Update Rollup 9 packages for Console and Serverand the Update Rollup 8 packages for Web Console, Gateway, Agent, and ACS. Or download the update packages from the Microsoft Update Catalog for Console and Server from Microsoft Download Catalog for Update Rollup 9, and download the update packages for Web Console, Gateway, Agent, and ACS from Microsoft Download Catalog for Update Rollup 8.
   
   
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. Run the flowing Datawarehouse SQL script on Datawarehouse Server against OperationsManagerDW database:
   
   
   UR_Datawarehouse.sql
   
   Note This script resides in the following location:
   
   
   %SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server\SQL Script for Update Rollups
   
   
4. Run 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.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.Visualization.Component.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

UNIX and Linux Management Pack Update

1. Apply Update Rollup 9 to your System Center 2012 SP1 Operations Manager environment.
2. Download the updated management packs for System Center 2012 SP1 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.

Operations Manager

UNIX and Linux Management Pack Update