UR#5 System Center 2012 R2 Released

A day ago Microsoft released Update Rollup package #5 for System Center 2012 R2.

This time the KB approach is different, compared to previous UR releases:

1. KB3021802
   Describes which components are updated in UR#5 for System Center 2012 R2. Per component another KB is available.
2. KB3023138
   Describes UR#5 for SCOM 2012 R2.

Issues which are fixed or newly added features

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

Installation order and instructions
Since Kevin Holman has written excellent postings about this topic in the past, there is no need to repeat myself. Here you can find Kevin’s posting about how to apply UR#3 for SCOM 2012 R2. This method is exactly the same for applying UR#5, so you can use that posting as an excellent reference for applying UR#5.

Be careful
Like I stated before with other Update Rollups, be careful. Test it first before you apply this newest UR. And when you don’t have a test environment or your test environment isn’t a good enough representation of your production environment, simply wait a few weeks before applying it.

Another advice: Download the UR pieces on the day you’re going to apply the UR and not weeks before. This way you’re 100% sure you’ve got the most recent UR bits and not an old set of it which has been replaced by a new set containing fixes for reported issues.