Monday, December 4, 2017

Update Rollup 14 for SCOM 2012 R2 Now Available

Last week Microsoft announced the release of Update Rollup 14 (UR14) for SCOM 2012 R2.


The Fixes

This latest update is as lightweight as they come and contains just a single key fix/enhcancement:

Update Rollup 14 for System Center components adds support for Transport Layer Security (TLS) protocol version 1.2. For more information about how to set up, configure, and run your environment to use TLS 1.2, see the following article in the Microsoft Knowledge Base:

4055768 TLS 1.2 Protocol Support Deployment Guide for System Center 2012 R2


The Gotcha's

The Web Console component of this update has the same known issue that we've seen with both UR13 for SCOM 2012 R2 and UR4 for SCOM 2016 whereby, after applying the update your web console's Silverlight configuration breaks! Here's a description of the issue:

When you access Silverlight dashboards, a “Web Console Configuration Required” message is displayed.

To work around the Silverlight dashboard issue, you'll need to work through the following steps:
  1. Click Configure in the dialog box.
  2. When you are prompted to run or save the SilverlightClientConfiguration.exe file, click Save.
  3. Run the SilverlightClientConfiguration.exe file.
  4. Right-click the .exe file, click Properties, and then select the Digital Signatures tab.
  5. Select the certificate that has Digest Algorithm as SHA256, and then click Details.
  6. In the Digital Signature Details dialog box, click View Certificate.
  7. In the dialog box that appears, click Install Certificate.
  8. In the Certificate Import Wizard, change the store location to Local Machine, and then click Next.
  9. Select the Place all certificates in the following store option and then select Trusted Publishers.
  10. Click Next and then click Finish.
  11. Refresh your browser window.

My Advice

As usual, my advice for deploying this update is to head over to Kevin Holman's blog and check out his handy step-by-step guide to get this up and running in your non-production environments first.