Exchange 2013 CU14 has been released to the Microsoft download centre! Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 SP1 was in effect CU4, and CU14 is the tenth post SP1 release.

This is build 15.00.1236.003 of Exchange 2013 and the update is helpfully named Exchange2013-x64-cu14.exe. Which is a great improvement over the initial CUs that all had the same file name! Details for the release are contained in KB 3177670.

Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version. This will dictate if the AD Schema needs to be modified. Check the values as noted in this post. There may be additional RBAC definitions, so PrepareAD should be executed prior to installing CU14. If setup detects that PrepareAD is required it will be automatically executed if the account running setup has the necessary permissions. This was an issue discussed in the MessageCopyForSentAsEnabled post.

Updates Of Particular Note

Exchange 2013 CU14 contains the security fix for MS16-108- Security update for Microsoft Exchange.

In addition the latest time zone updates are also included with CU14.

Exchange 2013 servers are no longer unexpectedly marked as offline. Using the setup wizard to upgrade an Exchange Server to a newer Cumulative Update causes an Exchange server to be marked offline in Exchange Active Monitoring during prerequisite analysis and prerequisite installation. If the setup wizard isn’t advanced to continue the upgrade process, the server will remain in an offline state until the setup is allowed to proceed. Also, if any of the setup /Prepare* switches are used to update Active Directory on a functional Exchange Server, the server is marked offline in Exchange Active Monitoring.

Exchange 2013 CU14 has not changed the current support stance for .NET framework. CU14 supports for .NET framework 4.6.1.

Issues Resolved

KB 3132513 “The Delegates settings were not saved correctly” when you try to add a user to Exchange Server 2013 from Microsoft Outlook

KB 3172017 “NotFound Export failed with error type: ‘NotFound'” error occurs when you perform an eDiscovery search in Exchange Server 2013

KB 3176377 Links to access Exchange items in SharePoint eDiscovery search result fail with an HTTP error 500 in Exchange Server

KB 3176540 OWA error reporting responds with a HTTP error 500 in OwaSerializationException

KB 3176873 Can’t create a new profile or connect to Exchange Server 2013 when an organization contains many address lists

KB 3061079 RPC Client Access service crashes and Event 4999 is logged in Exchange Server 2013

KB 3134918 An IRM-protected message sent to an external contact isn’t returned in a search or discovery results when journaling is implemented in an Exchange Server 2013 environment

KB 3190887 Upgrading Exchange Server causes the server to go offline unexpectedly

Some Items For Consideration

As with previous CUs, CU14 follows the new servicing paradigm which was previously discussed on the blog. The CU14 package can be used to perform a new installation, or to upgrade an existing Exchange Server 2013 installation to CU14. You do not need to install Cumulative Update 4 or 5 for Exchange Server 2013 when you are installing CU14. Cumulative Updates are well, cumulative. What else can I say…

After you install this cumulative update package, you cannot uninstall the cumulative update package to revert to an earlier version of Exchange 2013. If you uninstall this cumulative update package, Exchange 2013 is removed from the server.

Place the server into maintenance mode prior to installing, confirm the install then take the server out of maintenance mode

Restart the server after installing the CU

Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment. This includes archive, backup, mobility and management services.

Ensure that you do not forget to install this update on management servers, jump servers/workstations and application servers where the management tools were installed for an application. FIM and 3rd party user provisioning solutions are examples of the latter.

Ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed. See KB981474.

Disable file system antivirus prior to installing.

Once server has been restarted, re-enable file system antivirus.

Note that customised configuration files are overwritten on installation. Make sure you have any changes fully documented!

While CU14 does not add any new AD Schema changes, if you are on an out-dated CU currently then deploying CU14 may contain AD Schema updates for your organisation – please test and plan accordingly! Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version. This will dictate if the AD Schema needs to be modified. Check the values as noted in this post.

Please enjoy the update responsibly!

What do I mean by that? Well, you need to ensure that you are fully informed about the caveats with the CU and are aware of all of the changes that it will make within your environment. Additionally you will need to test the CU your lab which is representative of your production environment.

Cheers,

Rhoderick