On June 19, 2016 Microsoft released Exchange 2016 CU10 and Exchange 2013 CU21, exactly 90 days after the previous CUs. Perfectly aligned with their regular quarterly release 🙂
Besides regular hotfixes there are a couple of important things to notice:
- Exchange 2016 CU10 and Exchange 2013 CU21 need the .NET Framework 4.7.1. This is a hard requirement, so if .NET Framework 4.7.1 is not installed, the setup application will halt and generate an error message. You can use the Get-DotnetVersion.ps1 script that fellow MVP Michel de Rooij wrote to check the .NET version in advance.
- A new requirement is the VC++ 2013 runtime library. This component provides WebReady Document Viewing in Exchange Server 2010 and 2013 and Data Loss Prevention in Exchange Server 2013 and 2016. In the (near) future the VC++ 2013 runtime library will be forced to install.
- Standard support for Exchange 2013 ended on April 10th, 2018 and thus Exchange 2013 entered extended support. Exchange 2013 CU21 is the last planned CU. Customers need to install this CU to stay in a supported configuration, and to be able to install future Security Releases.
- When running a hybrid configuration with Exchange Online, customers are required to install the latest Cumulative Update for Exchange 2013 or Exchange 2016, or install the latest Update Rollup for Exchange 2010 SP3.
- None of these releases bring Active Directory Schema changes. You have to run Setup.exe /PrepareAD to activate new features like the following:
- A new feature in Exchange 2016 CU10 and Exchange 2013 CU21 is the option to create shared mailboxes in Office 365 using the *-RemoteMailbox cmdlets. For example, after creating a user account in Active Directory you can use the following command to create a Shared Mailbox in Office 365 directly:
Enable-RemoteMailbox -Identity <account> -Shared -RemoteRoutingAddress firstname.lastname@example.org
Microsoft also released Update Rollup 22 for Exchange 2010 SP3. This Update Rollup brings support for Windows 2016 Domain Controllers (and corresponding Domain Functional Level and Forest Functional Level) and it fixes an issue with Web Services impersonation.
As always you should thoroughly test the new Cumulative Updates or Update Rollups in your test environment before installing in your production environment.
Installing a Cumulative Update hasn’t changed much over the years, so you can follow my previous blogpost about installing Exchange 2013 CU9, which is especially important when installing a Cumulative Update in a Database Availability Group.
More information and downloads:
- Exchange 2016 CU10 (KB article) – https://support.microsoft.com/kb/4099852
- Exchange 2016 CU10 download – https://www.microsoft.com/download/details.aspx?id=57068
- Exchange 2016 CU10 UM Language Pack download – https://www.microsoft.com/download/details.aspx?id=57067
- Exchange 2013 CU21 (KB article) – https://support.microsoft.com/KB/4099855
- Exchange 2013 CU21 download – https://www.microsoft.com/en-us/download/details.aspx?id=57069
- Exchange 2013 CU21 UM Language Pack download – https://www.microsoft.com/download/details.aspx?id=57066
- Exchange 2010 SP3 Update Rollup 22 (KB article) – https://support.microsoft.com/KB/4295699
- Exchange 2013 Sp3 Update Rollup 22 (download) – https://www.microsoft.com/download/details.aspx?id=57065