Microsoft released today the Cumulative Update (CU) 6 for Microsoft Exchange Server 2016 (Download here).
It fixed the known issues:
- KB4024658 FIX: The EAS web.config file is not updated on the CAFE server during a build-to-build upgrade
- KB4024654 POP/IMAP clients can’t log on with NTLM when Alias and SamAccountName are different in Exchange Server 2016
- KB4024653 Active Monitoring probes fail when you use a new accepted domain as the default domain in Exchange Server 2016
- KB4024652 Repeated IMAP SEARCH BODY requests may not return newly delivered messages in Exchange Server
- KB4024651 The “MessageRetrievalMimeFormat” setting isn’t honored for plain text-only email messages in IMAP in Exchange Server
- KB4024650 Emoji is displayed as question marks in iOS clients in an Exchange Server environment
- KB4024649 The Read or Unread flag isn’t synchronized correctly after you turn off an ActiveSync device overnight in Exchange Server
- KB4024648 FIX: A new contact created in OWA may be merged into an existing contact on Exchange Server 2016
- KB4019534 Error when a mailbox name includes an umlaut in Exchange Server 2016 Cumulative Update 5
It additional brings the following new features:
- TLS 1.2 Support
- Original Folder Item Recovery
- Sent Items Behaviour Control
The CU 6 require the .NET 4.6.2 as outlined here. So you need to update to CU4 + .NET 4.6.2 at first before you can upgrade to CU6. So the best option to upgrade to Cumulative Update (CU) 6 for Microsoft Exchange Server 2016 is therefore the following:
Disable any 3rd party integration here like Backup, Logfile collectors (e.g. Splunk), Monitor environments (e.g. Nagios / NSCP Client), … before you start with the upgrade!
– Install Cumulative Update (CU) 4 for Microsoft Exchange Server 2016
– Upgrade to .NET Framework 4.6.1/4.6.2 (To to check which .NET Framework you have installed you could check here.) [You need to reboot the Server here!]
– Install Cumulative Update (CU) 6 for Microsoft Exchange Server 2016
Keep noted that using .NET Framework 4.7 on Exchange 2016 CU 6 (or older) is still unsupported (as written here) and might cause issues during the upgrade process!
