Earlier this month was a big day for Exchange updates. Not only did we get Cumulative Update 13 for Exchange 2013, but we also got our second update for Exchange 2016.
As always, test these updates in a lab first! I recommend checking out this 7-part guide on configuring Exchange in your lab. It doesn’t take much to get one going.
The updates are as follows:
Update: Special thanks to Keith Kroslow who pointed out that Exchange 2010 and 2007 did get an update. Their updates fix a potential elevation issue for Oracle products installed on an Exchange server. Check out KB 3151097 for 2010 and KB 3151086 for 2007.
So what’s new?
This update is a culmination of bug fixes and feature tweaks. Most notably we now see official support for .NET 4.6.1. The lack of support became a particular issue when Windows Updates began recommending this update back in February. Thankfully all stability issues have since been resolved. Microsoft recommends updating to CU2 and CU13 before installing .NET 4.6.1.
In the last update, we saw the end of SHA-1 certificates for S/MIME. This update follows suit by dropping SHA-1 from Exchange’s self-signed certificates. To get this added security you will need to regenerate your existing self-signed certificates. SHA-2 will be deployed by default for newly installed Exchange servers.
Another important update is the resolution of potential data loss when migrating public folders. You can read more about it in KB 3161916.
We also see added support for BitLocker during AutoReseed operations. Up to this point, you had to manually encrypt a hot spare either before or after an AutoReseed operation. With this update, we can now have Disk Reclaimer automatically encrypt the drive during AutoReseed operations. You will need to enable this functionality on your DAG.
C:\> Set-DatabaseAvailabilityGroup <Name> -AutoDagBitLockerEnabled $true[Read more…] about Exchange June 2016 Updates