Monday, January 30, 2017

Update Rollup 12 (UR12) Just Released for SCOM 2012 R2

Today, Microsoft released Update Rollup 12 for SCOM 2012 R2. This update contains a decent number of fixes along with some new enhancements for both Windows and cross-platform monitoring scenarios.

A full list of all the fixes and enhancements can be seen here:

I've yet to deploy this update into my lab but I'm particularly intrigued by this one:

  • Because of incorrect computations of configuration and overrides, some managed entities go into an unmonitored state. This behavior is accompanied by event 1215 errors that are logged in the Operations Manager log.

I've noticed managed entities going into an unmonitored state after applying overrides or changing distributed application configurations a lot over the last couple of years and it'll be interesting to see if this update sorts out the issue.

As should be the case for everyone deploying this update, test it in non-production environments first and be sure to read through Kevin Holman's excellent step-by-step guide to understand the order for which to apply the update and the additional manual steps that are needed:

Friday, January 27, 2017

KB 3216755 contains a fix for Windows Server 2016 monitoring with SCOM

I've just noticed a new Microsoft KB article (KB3216755) that points to an update that contains a fix for some scenarios where monitoring Windows Server 2016 or Windows 10 might fail.

I haven't come across the exact scenario (yet) that this fix applies to, but it's useful to know there's an update that can help if you run into problems.

Also, be sure to take a read of the 'Known Issues' section towards the end of the KB article where it states:

"The Cluster Service may not start automatically on the first reboot after applying the update."

The workaround for this known issue is to either use PowerShell to start the cluster service on the node you've applied the update to or simply to reboot the node once more.

Check out the KB article here for more info: