Today, the Exchange Team released the March updates for Exchange Server 2013 and 2016, as well as Exchange Server 2010 and 2007. The latter will receive its last update, as Exchange 2007 will reach end-of-life April 11, 2017.
As announced in December updates, Exchange 2013 CU16 and Exchange 2016 CU5 require .NET 4.6.2. The recommended upgrade paths:
- If you are still on .NET 4.6.1, you can upgrade to .NET 4.6.2 prior of after installing the latest Cumulative Update.
- If you are on .NET 4.52, upgrade to Exchange 2016 CU4 or Exchange 2013 CU15 if you are not already on that level, then upgrade to .NET 4.6.2, and finally upgrade to the the latest Cumulative Update.
The Cumulative Updates also include DST changes, which is also contained in the latest Rollups published for Exchange 2010 and 2007.
For a list of fixes in these updates, see below.
|
Exchange 2016 CU5 |
15.1.845.34 |
|||
|
Exchange 2013 CU16 |
15.0.1293.2 |
|||
|
Exchange 2010 SP3 Rollup 17 |
14.3.352.0 |
|||
|
Exchange 2007 SP3 Rollup 23 |
8.3.517.0 |
Exchange 2016 CU5 fixes:
- KB4015665 SyncDelivery logging folders and files are created in wrong location in Exchange Server 2016
- KB4015664 A category name that has different case-sensitivity than an existing name is not created in Exchange Server 2016
- KB4015663 “The message content has become corrupted” exception when email contains a UUE-encoded attachment in Exchange Server 2016
- KB4015662 Deleted inline picture is displayed as attachment after you switch the message to plain text in Exchange Server 2016
- KB4015213 Email is still sent to Inbox when the sender is deleted from the Trusted Contacts list in Exchange Server 2016
- KB4013606 Search fails on Exchange Server 2016 or Exchange Server 2013
- KB4012994 PostalAddressIndex element isn’t returning the correct value in Exchange Server 2016
Exchange 2013 CU16 fixes:
- KB4013606 Search fails on Exchange Server 2016 or Exchange Server 2013
- Exchange 2010 Rollup 17 fixes:
- KB 4014076 Migration ends and errors reported when you on-board or off-board a mailbox through Exchange Online in an Exchange Server 2010 hybrid environment
- KB 4014075 UNC path does not open in OWA when the path contains non-ASCII characters in an Exchange Server 2010 environment
- KB 4013917 You cannot search in a shared mailbox through OWA in an Exchange Server 2010 Service Pack 3 (Update Rollup 15 or 16) environment
- KB 4012911 Culture element is added in the wrong order when you use the ResolveNames operation in EWS in Exchange Server 2010
Notes:
Exchange 2016 CU5 doesn’t include schema changes, however, Exchange 2016 CU5 as well as Exchange 2013 CU16 may introduce RBAC changes in your environment. Where applicable, use setup /PrepareSchema to update the schema or /PrepareAD to apply RBAC changes, before deploying or updating Exchange servers. To verify this step has been performed, consult the Exchange schema overview.
When upgrading your Exchange 2013 or 2016 installation, don’t forget to put the server in maintenance mode when required. Do note that upgrading, before installing the Exchange binaries, setup will put the server in server-wide offline-mode.
Using Windows Management Framework (WMF)/PowerShell version 5 on anything earlier than Windows Server 2016 is not supported. Don’t install WMF5 on your Exchange servers running on Windows Server 2012 R2 or earlier.
When using Exchange hybrid deployments or Exchange Online Archiving (EOA), you are allowed to stay at least one version behind (n-1).
- If you want to speed up the update process for systems without internet access, you can follow the procedure described here to disable publisher’s certificate revocation checking.
- Cumulative Updates can be installed directly, i.e. no need to install RTM prior to installing Cumulative Updates.
- Once installed, you can’t uninstall a Cumulative Update nor any of the installed Exchange server roles.
- The order of upgrading servers with Cumulative Updates is irrelevant.
Caution: As for any update, I recommend to thoroughly test updates in a test environment prior to implementing them in production. When you lack such facilities, hold out a few days and monitor the comments on the original publication or forums for any issues.