Exchange Quarterly Updates 2016

Microsoft have released their latest quarterly updates for Exchange Server 2013 and 2016. Cumulative Update 13 is now available for Exchange Server 2013, and Cumulative Update 2 for Exchange Server 2016. Both updates add additional functionality to Exchange Server as well as fixing bugs. The updates include the changes in the previous Cumulative Updates for each product. One of the main additions in these updates is the support for .NET 4.6.1. Microsoft recommends applying the Cumulative Update before installing .NET 4.6.1. These updates also add support for BitLocker for the Disk Reclaimer function within AutoReseed. The default setting for this is off however. Cumulative Update 2 for Exchange Server 2016 includes fixes for the following 6 headline items:

  • Restores ability to search emails in Outlook and Outlook Web App that was not working in some Exchange Server 2016 CU1 environments
  • Cannot connect to mailbox when MAPI over HTTP protocol is in use
  • Email body is garbled when Simplified Chinese characters are included on BCC address line
  • Failed to load script error when logging on to Outlook Web App
  • Fix for potential data loss when migrating Public Folders
  • Fix for Retention policy not working on In-Place Archive mailboxes

Cumulative Update 2 also includes updates to Daylight Saving Time, the security changes outlined in MS16-079, as well as the changes in Cumulative Update 1. Cumulative Update 13 for Exchange Server 2013 includes substantially more fixes than the 2016 update. As well as the Daylight Saving Time changes, the security changes outlined in MS16-079, and the changes in previous Cumulative Updates, this release includes 21 listed fixes. The full list of 21 fixes are described on the Microsoft support site so we won’t repeat them here. Examine the changes and fixes contained in these latest updates and then decide if deploying them would benefit your organization. Make sure that you fully test these updates in your Testing environment before rolling out to Production servers. Some environments will require server restarts after the updates are applied. So deployment should be planned for Production at a time when a system restart will not adversely affect messaging services.