Catching up on some news from last month, Microsoft has announced the latest quarterly updated for Exchange Server 2016 and 2013.
- Cumulative Update 7 for Exchange Server 2016 (download | UM language pack)
- Cumulative Update 18 for Exchange Server 2013 (download | UM language pack)
Exchange 2016 CU7 enforces a minimum forest functional level of Windows Server 2008 R2. The support requirement for FFL of 2008R2 has actually existed since Exchange 2016 CU3, but CU7 is the first CU to enforce it.
There is no change in .NET Framework 4.7.x support with these CUs. .NET 4.7.x remains unsupported for now, and should not be deployed to Exchange servers. The Exchange team plans to include support for .NET 4.7.1 (not 4.7.0) in the December 2017 CU releases, and will require .NET 4.7.1 from June 2018 onwards. You should check your .NET Framework versions and make a plan to upgrade to stay within the supported scenarios listed on the supportability matrix. The Exchange Analyzer tool can help flag .NET/Exchange compatibility issues in your environment.
The comments of the Exchange team blog post call attention to a few issues that customers are experiencing rolling out these updates. As always, you should test CU releases before you deploy them to your production servers.
- Best Practices: Keeping Exchange Servers Updated
- FAQ: In What Order Should You Install Service Packs, Update Rollups, and Cumulative Updates?
- Installing Cumulative Updates on Exchange Server 2016
- Installing Cumulative Updates on Exchange Server 2013