Update Rollup 2 For SCOM 2012 R2 Is Out!

Just now Microsoft released Update Rollup 2 for SCOM 2012 R2, to be found in KB2929891.

This UR#2 fixes 9 issues:

1. Issue 1
   This update rollup makes the stored procedure performance aggregate more robust against out-of-range values.
2. Issue 2
   Adding multiple regular expressions (RegEx) to a group definition causes an SQL exception when the group is added or run.
3. Issue 3
   Web applications fail when they are monitored by the System Center Operations Manager 2012 R2 APM agent.
4. Issue 4
   Service Level Objectives (SLO) dashboards sometimes load in several seconds and sometimes take minutes to load. Additionally, the dashboard is empty after it loads in some cases.
5. Issue 5
   Operations Manager Console crashes when you try to override the scope in the Authoring pane.
6. Issue 6
   The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.
7. Issue 7
   This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 1.
8. Issue 8
   SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse workflows.
9. Issue 9
   This update rollup includes a fix for the Event Data source.

Good to know is that this UR#2 requires additional manual actions, just like UR#1 for SCOM 2012 R2. So my advice is NOT to use the automated update feature but to roll out this UR#2 manually on a time schedule which suits your organization and you best.

This update also contains a fix for the data warehouse BULK insert commands timeout issue. This fix consists out of a registry key which must be manually added on any SCOM 2012 R2 UR#2 MS server on which you wish to override the default bulk insert command timeout. The procedure for adding this registry key is described in the same KB article.

Again, just like my advice for UR#1 for SCOM 2012 R2, wait with rolling out this UR in your production environment. Test it first in your test environment when you’ve got any. And when you don’t just wait as well before applying this UR. it wouldn’t be the first time some nasty side effects got through QC at Microsoft resulting in broken environments.