On December 19th, Microsoft released the latest round of quarterly updates. This round includes updates for Exchange 2010, Exchange 2013 and Exchange 2016.
Exchange 2010 Update Rollup 19
This update is a security fix for Exchange 2010/2016 coexistence scenarios. According to Microsoft it fixes an issue where proxied EWS calls could gain access to a 2010 mailbox that a user shouldn’t have access to. If you have deployed Exchange 2010 and 2016 together, you should make this patch a priority.
Exchange 2013 CU 19 and Exchange 2016 CU8
- .Net 4.7.1 support has been included. It should be mentioned that you should be looking to upgrade because .Net 4.7.1 will be a requirement for the June 2018 updates. .Net 4.7.0 is not, and will not be supported.
- Support for Hybrid Modern Authentication has been released to Exchange 2013 and Exchange 2016.
- Applying CUs will no longer overwrite any TLS and cryptography configurations made on the servers, keeping us from having to re-apply custom settings after every update.
None of the updates released contain any updates to AD Schema.
And as always, remember to test these updates in a test environment before applying them to your production servers. It’s best practice and really the only good way to limit the possible headaches that Exchange updates can cause.