Exchange 2013 CU21 Released


Exchange 2013 CU21 has been released to the Microsoft download centre!

Download Exchange 2013 CU21

This is build 15.00.1395.004 of Exchange 2013 and the update is helpfully named Exchange2013-x64-cu21.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 4099855.

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 CU22.  If setup detects that PrepareAD is required it should be automatically executed if the account running setup has the necessary permissions.  This was an issue first discussed in the MessageCopyForSentAsEnabled  post and in Unexpected Exchange AD Object Values.

Cumulative Update 21 is the last planned quarterly update for Exchange Server 2013. Customers must upgrade to Cumulative Update 21 to continue to receive future security updates.

Exchange 2007 is no longer supported, updates are not provided once a product has exited out of extended support.

Updates Of Particular Note

.NET framework 4.7.1 is now required.  This was previously discussed in the December 2017 release of Exchange updates.

Exchange 2013 CU21 and onwards will require the VC++ 2013 runtime library installed on the server.

The below updates will be of use to many customers running in an Exchange hybrid deployment.

4058473 An Office 365 primary mailbox user cannot be assigned full access permissions for an on-premises mailbox in Exchange Server

4133605 Cmdlets to create or modify a remote shared mailbox in an on-premises Exchange environment

Starting in Cumulative Update 21 for Exchange Server 2013 and Cumulative Update 10 for Exchange Server 2016 in an on-premises Exchange Server environment, you can directly create or modify a remote shared mailbox by using the new parameter -shared with the following cmdlets:

  • Enable-RemoteMailbox: [-Identity user] [-Shared] [-RemoteRoutingAddress user@domain]
  • New-RemoteMailbox: [-Shared] [-Name RemoteMailboxName]
  • Set-RemoteMailbox: [-Name user] [-Type Shared]

Note – if after installing the CU you do not see the new –Shared parameter then the step to manually run /PrepareAD was not done.  Read the rest of this post for details on that issue.

CU21 also includes the latest DST updates.

Issues Resolved

4133605 Cmdlets to create or modify a remote shared mailbox in an on-premises Exchange environment

4133604 User can’t log on to a POP/IMAP account by using NTLM authentication in Exchange Server 2013

4133618 Unexpected error occurs when running the Get-DatabaseAvailabilityGroupNetwork cmdlet in Exchange Server 2013

4133620 “HTTP 500 due to ADReferralException” when a user tries to view detail properties of mailboxes in a child domain in Exchange Server

4058473 An Office 365 primary mailbox user cannot be assigned full access permissions for an on-premises mailbox in Exchange Server

4094167 The MSExchangeRPC service crashes with a System.NullReferenceException exception in Exchange Server 2013

4095974 “System.InvalidOperationException” occurs when the “Enable-MailPublicFolder” cmdlet is run against a public folder in Exchange Server

4092041 Description of the security update for Microsoft Exchange Server 2013 and 2016: May 8, 2018

4294205 POP3 services intermittently stop in an Exchange Server 2013 environment

4294204 Changing “IsOutOfService” to “False” in an earlier Exchange Server version does not immediately update in a later Exchange Server environment

Free subscription



You may also like...

Geef een reactie

Het e-mailadres wordt niet gepubliceerd. Vereiste velden zijn gemarkeerd met *