Update Rollup 5 for System Center 2012 R2 Operations Manager

No Comments on Update Rollup 5 for System Center 2012 R2 Operations Manager

The Update Rollup 5 für System Center 2012 R2 Operations Manager come swith lots of fixes and there is somethin to pay attention while installing.


  • Monitoringhost process crashes because of bind failures against Active Directory
  • RunAs accounts cannot be edited because of „Specified cast is invalid“ exception
  • Application crashes when a search is finished without filter criteria on Distributed application designer
  • MonitoringHost crashes with the exception – System.OverflowException: Value was either too large or too small for an Int32
  • Support to troubleshoot PowerShell scripts
  • Operational Insights through Operations Manager
  • „Reset the Baseline,“ „Pause the baseline,“ and „Resume the baseline“ tasks fail when they are run against an Optimized performance collection rule
  • An exception occurs when you edit subscriptions that contain deleted monitors or objects
  • You can’t set Widget column width
  • Event 4506: Data was dropped because of too much outstanding data
  • Support for handling Datawarehouse time-outs
  • Can’t continue scan with NOLOCK because of data movement
  • $ScriptContext.Context does not persist the value in PowerShell widgets
  • Evaluation version alert


When installing UR5 you have to follow these steps::

  1. Install the update rollup package on the following server infrastructure:
      Management server or servers
      Gateway servers
      Web console server role computers
      Operations console role computers
  2. Apply SQL Scripts (located under %SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\SQL Script for Update Rollups )
      UR_Datawarehouse.sql against OperationsManagerDW database
      Update_rollup_mom_db.sql against OperationsManager database
  3. Import Management Packs (located under %SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups )
  4. Update SCOM Agents


To enable the web console fixes, add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:

Do not install this update rollup package immediately after you install the System Center 2012 R2 server. Otherwise, the Health Service state may not be initialized.

Related Posts

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Back to Top