• Adrian Dolder

Exchange 2016 CU8 / Exchange 2013 CU19

Updated: May 3, 2019


The 19th december 2017, Microsoft released the new Cumulative Updates.

Informations can be found on the links below (Exchange Team Blog).

Downloads:

Exchange 2016 CU8

Exchange 2013 CU19

Information: For all, having the same problem after the installation of the KB4045655 (Security Update for Exchange) as described in my previous blogpost --> on my test environment, the issues are gone after installation of the Exchange 2016 CU8.

Attention: If you have a Database Availability Group (DAG) and want to make your maintenance with the preinstalled script "StartDAGServerMaintenance.ps1" - Check out my blogpost "Exchange DAG Maintenance - cluster.exe issue (5058)", because the issue still persist (also after the CU8/CU19 installation.

What's new: Exchange 2016 CU8 (quotes from Exchange Team Blog)

  • .NET framework 4.7.1 is now fully supported. Currently this is an optional item, but will be required with a future CU. Plan accordingly! Customers should test, verify and install CU8 then move to update to .NET 4.7.1 which will be required for the June 2018 CU install. --> ATTENTION: .NET 4.7 is not supported, it is only .NET 4.7.1 after the install of CU8!

  • CU8 introduces a change in TLS and cryptography settings. Previous CUs would overwrite a custom configuration. TLS and cryptography is now configured at install time and future CUs should not overwrite customisations .

  • Hybrid Modern Authentication (not HAM) provides users the ability to access on-premises applications using authorisation tokens obtained from Office 365. These OAuth tokens allow access to authenticate against on-premises Exchange.

  • If you are in an environment where Exchange 2016 coexists with Exchange 2010, then please also review Exchange 2010 SP3 RU19 as you will need to install that update on Exchange 2010 to resolve a proxy issue.

  • As per Active Directory Forest Functional Levels for Exchange Server 2016, it was announced that Exchange Server 2016 would enforce a minimum 2008R2 Forest Functional Level requirement for Active Directory. Cumulative Update 7 for Exchange Server 2016 will now enforce this AD DS requirement.

Issues Resolved Exchange 2016 CU8

  • 4056329 Can't access EWS from Outlook/OWA add-ins via makeEwsRequestAsync in Exchange Server 2016 and Exchange Server 2013

  • 4054516 "Your request can't" error when accessing an archive mailbox via OWA in Exchange Server 2016

  • 4055953 The recipient scope setting doesn't work for sibling domains in Exchange Server 2016

  • 4055435 No MAPI network interface is found after you install Exchange Server 2016 CU7

  • 4056609 Event ID 4999 and mailbox transport delivery service does not start after you install Exchange Server 2016 CU7

  • 4045655 Description of the security update for Microsoft Exchange: December 12, 2017

  • 4057248 Many Watson reports for StoragePermanentException in Exchange Server 2016

What's new: Exchange 2013 CU19 (quotes from Exchange Team Blog)

  • .NET framework 4.7.1 is now fully supported. Currently this is an optional item, but will be required with a future CU. Plan accordingly! Customers should test, verify and install CU19 then move to update to .NET 4.7.1 which will be required for the June 2018 CU install. --> ATTENTION: .NET 4.7 is not supported, it is only .NET 4.7.1 after the install of CU8!

  • CU19 introduces a change in TLS and cryptography settings. Previous CUs would overwrite a custom configuration. TLS and cryptography is now configured at install time and future CUs should not overwrite customisations .

  • Hybrid Modern Authentication (not HAM) provides users the ability to access on-premises applications using authorisation tokens obtained from Office 365. These OAuth tokens allow access to authenticate against on-premises Exchange.

Issues Resolved Exchange 2013 CU19

  • 4046316 MAPI over HTTP can't remove client sessions timely if using OAuth and the resource has a master account in Exchange Server 2013

  • 4046205 W3wp high CPU usage in Exchange Server 2013

  • 4046182 Event ID 4999 or 1007 if diagnostics service crashes repeatedly in Exchange Server 2013

  • 4056329 Can't access EWS from Outlook/OWA add-ins via makeEwsRequestAsync in Exchange Server 2016 and Exchange Server 2013

  • 4045655 Description of the security update for Microsoft Exchange: December 12, 2017

#Maintenance #ExchangeDAG #ExchangeMaintenance #Exchange #Exchange2016 #Exchange2013 #CU8 #CU19 #Exchange2016CU8 #Exchange2013CU19

Talking Microsoft

A BLOG ABOUT EXCHANGE, SKYPE FOR BUSINESS, OFFICE 365 AND MORE
DOUDISBLOG
  • Doudisblog on Facebook
  • Doudisblog on Twitter
  • Mail
  • Doudisblog RSS
  • Doudisblog Youtube Channel
  • Adrian Dolder - LinkedIn
  • Xing_Button
  • Doudisblog
  • Doudisblog on Facebook
  • Doudisblog on Twitter
  • Doudisblog RSS
  • Doudisblog Youtube Channel
  • Adrian Dolder - LinkedIn
  • Xing_Button

© 2019 by ADRIAN DOLDER - BLOG@DOUDI.CH - SWITZERLAND