Description of Update Rollup 3 for System Center 2012

Known issues for this update

• After you install the update rollup package on all roles on the System Center Operations manager 2012 server, except on the Agent and Gateway roles, the updates do not appear in the Add or Remove Programs item in Control Panel.

• After you install the update rollup package, the version number of the console is not changed. After you install Update Rollup 2 for System Center Operations Manager 2012, the version number of the console is 7.0.8560.0 as expected.

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

  Server Error in '/OperationsManager' Application.

  To resolve this issue, close and then restart Windows Internet Explorer.
  

• After you uninstall the update rollup package, a System.Management.Automation.ActionPreferenceStop exception occurs in the Discover Agent Versions script, and the script fails. To resolve this issue, change the InstallDirectory value in the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations" registry subkey to C:\Program Files\System Center 2012\Operations Manager\PowerShell.

Notes on installation

• The update rollup package is available from Microsoft Update in the following languages:

  • Chinese (Traditional)

  • English

  • French

  • German

  • Italian

  • Japanese

  • Portuguese (Brazil)

  • Russian

  • Spanish

  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 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 <system.web>, as described in the following Microsoft Knowledge Base (KB) article:

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

Supported installation order

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

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

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

   1. Management server or servers

   2. Gateway servers

   3. Reporting servers

   4. Web console server role computers

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

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

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 updates 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.
   
   Notes

   • The following 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 three MSP files on the management server. Apply one MSP file on a server for each specific role that the server holds.

   • Microsoft Update may append a GUID to the .cab files that contain the MSPs that are listed below. Go to the table that follows these instructions for a complete mapping of .cab GUIDs to each localized component update.

   • KB2750631-AMD64-Agent.msp

   • KB2750631-AMD64-Console.msp

   • KB2750631-AMD64-Gateway.msp

   • KB2750631-AMD64-Reporting.msp

   • KB2750631-AMD64-Server.msp

   • KB2750631-AMD64-WebConsole.msp

   • KB2750631-i386-Agent.msp

   • KB2750631-i386-Console.msp

   • KB2750631-ia64-Agent.msp

3. Import the following management packs:

   • Microsoft.SystemCenter.DataWarehouse.Library.mpb

   • Microsoft.SystemCenter.Visualization.Library.mpb

   • Microsoft.SystemCenter.WebApplicationSolutions.Library.mpb

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

How to Import an Operations Manager Management PackNote Management packs are included in the Server component updates in the following path:

%SystemDrive%\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update RollupsIf you have downloaded cabbed MSP files for a component in more than one locale, refer to the following table. The table lists GUIDs that are present in the .cab file name. You can refer to the table in order to determine which locale a cabbed MSP applies to.

Uninstall Information

To uninstall an update, run the following command:

msiexec /uninstall <PatchCodeGuid> /package <RTMProductCodeGuid>

Note In this command, RTMProductCodeGuid" is a placeholder for one of the following GUIDs:

Additionally, "PatchCodeGuid" is a placeholder for one of the following GUIDs: