[OpsMgr 2012] Update Rollup 1 for System Center 2012 - Operation Manager SP1

 Article ID: 2686249 - Last Review: May 7, 2012 - Revision: 3.1

 

Less than a month after the general availability of the product, Microsoft is delivering a first cumulative update package (CU1) for System Center Operations Manager 2012. He brings including support for Solaris 11 (x86 and SPARC).

This cumulative update (KB2686249) addresses the following issues :

 

 

 

Operations Manager Update (KB2674695) – Windows monitoringEnvironment crashes in Operations Manager because of RoleInstanceStatusProbe module in AzureMP.

2. When multiple (two or three) consoles are running on the same computer under the same user account, the consoles may crash.
3. You cannot start or stop tracing for Reporting and Web Console if they were installed to a stand-alone server that is running IIS.
4. Connected Group alert viewing is not working, but no error is given in console.
5. Task result - CompletedWithInfo not supported with the SDK2007 assemblies.
6. SeriesFactory and Microsoft.SystemCenter.Visualization.DatatoSeriesController have to be public to give the controls extensibility and reuse.
7. WebConsole is not FIPS compliant out of the box.
8. Network Dashboard should overlay Availability when displaying health state.
9. Dashboards: Group picker does not show all groups in large environment.
10. IIS Discovery: Prevent GetAdminSection from failing when framework version was detected incorrectly by IIS API.
11. Performance Counters are not displayed in the Application list view of AppDiagnostics.
12. Console crashes when state view with self-contained object class is opened.
13. PerformanceWidget displays stale "last value" in the legend because of core data access DataModel.
14. Availability Report and "Computer Not Reachable" Monitor display incorrect data.
15. Agent install fails on Win8 Core because of dependency on the .NET Framework 2.0.
16. Web Services Availability Monitoring Wizard - Console crashes if the wizard finishes before a test has finished.
17. Several Windows PowerShell changes are needed:

• Changed License parameter in Get-SCOMAccessLicense to ShowLicense
• Changed SCOMConnectorForTier cmdlets to SCOMTierConnector
• Some formatting changes

 

Operations Manager Update (KB2674695) – Unix and Linux monitoringSchannel error events are logged to the System log on Operations Manager Management servers and on gateways that manage UNIX/Linux agents.

2. On HP-UX, Operations Manager cannot discover and monitor a logical volume composed of more than 127 physical volumes.
3. Upgrade of UNIX and Linux agents fails when using Run As credentials in the Agent Upgrade Wizard or Update-SCXAgent Windows PowerShell cmdlet.

Operations Manager Update (KB2674695) – New featureUpdate Rollup1 for Operations Manager adds support for Oracle Solaris 11 (x86 and SPARC).

 

 

 

How to obtain and install Update Rollup 1 for System Center 2012

To download the update packages for Operations Manager, go to the following Microsoft Download Center website:

http://www.microsoft.com/downloads/details.aspx?FamilyID=c593536c-94f3-4c71-b963-5ab3b7fc05e1 (http://www.microsoft.com/downloads/details.aspx?FamilyID=c593536c-94f3-4c71-b963-5ab3b7fc05e1)

• To obtain and install the update packages from Microsoft Update, follow these steps on a system that has a Virtual Machine Manager or App Controller component installed:
  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 the important updates are available hyperlink.
  5. Select Update Rollup 1, and then click OK.
  6. Click Install updates to install the update package.

Installation instructions for Operations Manager

Known issues for this update

• No updates items appeared in Control Panel ARP after installing Update Rollup 1 (UR1). After installing UR1 on server and all roles (except Agent and Gateway), no update item appears in Control Panel ARP list.
• The version number of the console does not change after installing Update Rollup 1 in the UI. After installing Update Rollup 1 ,the version number of the console is still 7.0.8560.0 in the UI.
• After installing UR1 on web console, a Server Error in "/OperationsManager" Application appears in Internet Explorer. Closing and restarting Internet Explorer resolves this problem.

Notes on installation

• Operations Manager Update Rollup 1 will at first be available only in English and cannot be applied to non-English products. Fixes included in this UR will be localized in a future release.
• User must run updates as administrator.
• If UAC is enabled, MSPs must be run from an elevated command prompt window.
• System Administrator rights on the database instances for the Operational Database and Data warehouse are required in order to run updates on these databases.
• User has to close console before applying console update to avoid having to restart.
• Restart and clear cache of the browser to obtain new Silverlight instance.
• This UR should not be installed immediately after installing server. Otherwise, user could encounter an issue in which Health Service state remains uninitialized.
• Web console fixes will work after adding 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"/>
  
  The line should be added under <system.web>, as described in the following article in the Microsoft Knowledge Base:
  911722  (http://support.microsoft.com/kb/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 this update rollup in the following order.

Note This update rollup can be installed on agents either before or after server infrastructure.

1. Server infrastructure:
   1. Management server or servers
   2. Gateway servers
   3. Reporting servers
   4. Web console server role computer
   5. Operations console role computers
   6. Manually imported management packs
2. Apply the agent update to manually installed agents, or push installation from the Pending view in the Operations console.

Note If Connected MG/Tiering is enabled, the top tier should be patched first.

Installation Information

To extract the files that are contained in this update, follow these steps:

1. Copy the following file to either a local folder or an available network share, and then execute the file to extract it:
   SystemCenter2012OperationsManager-CU1-KB2674695-X86-X64-IA64-ENU.exe
2. Apply the appropriate MSPs to each computer. All MSPs that apply to a given computer must be applied. For example, if a Management Server also has Web Console and Console roles installed, three MSP packages should be applied to the Management Server. The following MSPs are included in the update:
3. • KB2674695-AMD64-Agent.msp
   • KB2674695-AMD64-Console.msp
   • KB2674695-AMD64-Gateway.msp
   • KB2674695-AMD64-Reporting.msp
   • KB2674695-AMD64-Server.msp
   • KB2674695-AMD64-WebConsole.msp
   • KB2674695-i386-Agent.msp
   • KB2674695-i386-Console.msp
   • KB2674695-ia64-Agent.msp
4. Import the following management packs:
   1. Microsoft.SystemCenter.DataWarehouse.Library.mpb
   2. Microsoft.SystemCenter.Visualization.Library.mpb
   3. Microsoft.SystemCenter.WebApplicationSolutions.Library.mpb
      
      For information about how to import a management pack from disk, go to the following Microsoft TechNet website:
      How to Import an Operations Manager Management Pack

This posting is provided "AS IS" with no warranties.