The latest set of Cumulative Updates for Exchange Server 2016 and Exchange Server 2013 are now available on the download center. These releases include fixes to customer reported issues, all previous...
Updated Jul 01, 2019
Version 2.0
Blog Post
If I remember correctly, last year at Ignite the Exchange team mentioned that Set-DatabaseAvailabilityGroup -AutoDagBitlockerEnabled that was implemented in CU2 did not actually work (yet). I have not seen anything public to that effect, acknowledging the problem or that it has been fixed. Can the team please point me in the right direction for documentation or speak to this?
https://blogs.technet.microsoft.com/exchange/2016/06/21/released-june-2016-quarterly-exchange-updates/
AutoReseed support for BitLocker
Beginning with Exchange 2013 CU13 and Exchange 2016 CU2, the Disk Reclaimer function within AutoReseed supports BitLocker. By default, this feature is disabled. For more information on how to enable this functionality, please see Enabling BitLocker on Exchange Servers.
- There was an issue with where if you were not leveraging a certificate for encryption purposes, you couldn't leverage BitLocker automatically with AutoReseed (instead you had to either format/encrypt disks prior to usage or encrypt after failure). That was resolved in CU5.
- Thank you Ross.