This update contains twenty documented fixes with the following few of particular interest to me (based on what I've come across on customer sites so far):
- When alerts are closed from the Alerts view after you run a Search, the closed Alerts still appear in the View when the Search is cleared.
- Groups disappear from Group view after they are added to a Distributed Application.
- When the maintenance mode option for the dependency monitor is set to “Ignore,” and the group (consisting of the server to which this dependency monitor is targeted) is put in Maintenance mode, the state of the monitor changes to critical and does not ignore maintenance mode.
- Because of a rare scenario of incorrect computation of configuration and overrides, some managed entities may go into an unmonitored state. This behavior is accompanied by 1215 events that are written to the Operations Manager log.
You can see the full list of fixes from the official UR2 knowledge base article here.
To get access to this update, you can choose to either manually download it from the Microsoft Update Catalog here or you can use Windows Update to pull down the update automatically to your SCOM 2016 environment.
Whatever method you choose to deploy this update, make sure to read through the full installation instructions as there are some manual tasks to carry out once the update has been applied to each SCOM role and if you're not confident, I'd always recommend waiting for Microsoft's Kevin Holman to add his walk-through post for this UR to his blog here.
Finally, this update is one part of a larger UR2 release for covering other products in the System Center 2016 suite. If you've deployed additional components of the suite alongside SCOM, then you might be interested to check out the updates now available for DPM 2016, SCSM 2016, SPF 2016 and SCVMM 2016.
Full details of all the fixes in the main System Center 2016 UR2 downloads can be viewed at:
No comments:
Post a Comment