Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1

Issues that are fixed in this update rollup

Operations Manager

• The Reset the baseline, Pause the baseline, and Resume the baseline actions fail when you run them against an optimized performance collection rule.
• The DeltaSynchronizationengine work item times out on SQL operations, and Event ID 29181 is generated.
• Running the Export-SCOMEffectiveMonitoringConfiguration cmdlet fails, and you receive the following error message:
  
  
  Subquery returned more than 1 value.
• Time zone settings are not added to subscriptions when non-English display languages are set.
• The Operations Manager dashboard experiences a performance issue that is caused by the TopNEntitiesByPerfGet stored procedure.

Known issues with this update

• After you install this 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 6, you have to reopen the Operations Manager console in order to apply the Alert Attachment Management Pack fix.
• After you install this update rollup package, the version number of the console is not changed.
• If the ACS update package is installed, uninstalled, and then re-installed, the database upgrade script that is included in this update will not run. This behavior occurs 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 with the partition still in place.
  
  The partition can be closed manually by going to the ACS database in Microsoft SQL Server Studio and then 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

  In order to create a new partition, stop the AdtServer service, run the script, and then restart the AdtServer service.
• After you install this update rollup package on a web console, you may receive the following error message in Internet Explorer:
  
  
  Server Error in '/OperationsManager' Application. To resolve this issue, close and then restart Internet Explorer.
• When you try to import Microsoft.SystemCenter.Visualization.Component.Library, the import fails because of missing dependencies.
  
  To resolve this issue, import Microsoft.SystemCenter.Visualization.Component.Library again.

How to obtain and install Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1

Download information

Microsoft Update

1. Click Start, and then click Control Panel.
2. In Control Panel, double-click Windows Update.
3. In the Windows Update window, click Check Online for updates from Microsoft Update.
4. Click Important updates are available.
5. Select the Update Rollup packages that you want to install, and then click OK.
6. Click Install updates to install the selected update packages.

Manual download of the update packages

Download the Operations Manager Service Pack 1 update package now.

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, you should 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, you should 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 is 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.
  
  The registry subkey is as follows:
  
  
  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 placeholder nn is a value in seconds. For example, set the value data to 40 for a 40-second time-out.

Installation instructions

Supported installation order

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.
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 following Datawarehouse SQL script on Datawarehouse server against the OperationsManagerDW database:
   • UR_Datawarehouse.sql
   Note The path of the script is as follows:
   
   
   %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
     
     Note This pack has the following dependencies:
     • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb which should be installed from SCOM 2012 SP1.
     • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which should be installed from the Microsoft 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

Uninstall information