250 Hello

Random Musings on Exchange and Virtualization

Exchange 2013 CU6 Released

Exchange 2013 CU6 Released

  • Comments 7
  • Likes

Exchange 2013 CU6 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 CU6 is the second post SP1 release.  CU6 contains AD DS schema changes so please test and plan accordingly!

Update 1-9-2014:  If you are deploying into a mixed environment with Exchange 2007, you need to review KB2997209 Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007

Update 1-9-2014: Please also review the comments here for an issue that affects Hybrid mailboxes. 

Update 9-9-2014: If you are deploying into a mixed environment with Exchange 2007, you also need to review KB 2997847 You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to Exchange 2013 CU6

Exchange 2013 CU6 Download

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

 

Updates Of Particular Note

  • CU6 includes significant improvements in Public Folder scalability
  • 2988229 Hybrid Configuration wizard error "Subtask CheckPrereqs execution failed" for Exchange Server 2013 (if you installed the IU, it does not have to be removed prior).
  • 2986779 EMS takes a long time to execute the first command in an Exchange Server 2013 Cumulative Update 5 environment
  • 2983512 RPC Client Access service crashes on an on-premises Mailbox server in an Exchange Server 2013 hybrid environment
  • 2975599 Exchange Server 2010 public folder replication fails in an Exchange Server 2013 environment
  • 2975003 Calendar item body disappears in Outlook online mode in an Exchange Server 2013 environment

 

Issues Resolved

  • 2991934 Duplicate mailbox folders after migration to Exchange Server 2013
  • 2988229 Hybrid Configuration wizard error "Subtask CheckPrereqs execution failed" for Exchange Server 2013
  • 2986779 EMS takes a long time to execute the first command in an Exchange Server 2013 Cumulative Update 5 environment
  • 2983512 RPC Client Access service crashes on an on-premises Mailbox server in an Exchange Server 2013 hybrid environment
  • 2983426 AutodiscoverSelfTestProbe fails when external URL is not set for EWS virtual directory in Exchange Server 2013
  • 2983423 AutodiscoverSelfTestProbe fails when external URL is not set for ECP virtual directory in Exchange Server 2013
  • 2983422 The ServerWideOffline component is set to Inactive after Exchange Server 2013 prerequisite check fails
  • 2983207 "532 5.3.2" NDR when you send an email message to a hidden mailbox in an Exchange Server 2013 environment
  • 2983066 Removed Default or Anonymous permission for Outlook folders cannot be restored in an Exchange Server 2013 environment
  • 2982769 "Topology service cannot find the OWA service" when you perform an eDiscovery search in Exchange Server 2013
  • 2982763 Mail-enabled public folder accepts email messages from unauthorized users in an Exchange Server 2013 environment
  • 2982762 OAB generation arbitration mailbox can be removed or disabled in an Exchange Server 2013 environment
  • 2982760 The Enter key submits duplicate sign-in forms to Outlook Web App in an Exchange Server 2013 environment
  • 2982759 You cannot access the archive mailbox of a delegated user after enabling MAPI over HTTP
  • 2982017 Incorrect voice mail message duration in an Exchange Server 2013 environment
  • 2981835 You cannot add attachments, delete or move many email messages in bulk in Outlook Web App
  • 2981466 MAPI/CDO client cannot connect to Exchange Server 2013
  • 2977279 You cannot disable journaling for protected voice mail in an Exchange Server 2013 environment
  • 2975599 Exchange Server 2010 public folder replication fails in an Exchange Server 2013 environment
  • 2975003 Calendar item body disappears in Outlook online mode in an Exchange Server 2013 environment
  • 2974339 OAB generation fails if FIPS is used in an Exchange Server 2013 environment
  • 2971270 Blank page after you sign in to Exchange Server 2013 EAC (formerly ECP)
  • 2970040 Folder Assistant rule does not work correctly in an Exchange Server 2013 environment
  • 2965689 EAS device cannot sync free/busy status if an item is created by EWS in an Exchange Server 2013 environment
  • 2963590 Message routing latency if IPv6 is enabled in Exchange Server 2013
  • 2961715 "Something went wrong" error in Outlook Web App may show an incorrect date
  • 2958434 Users cannot access mailboxes in OWA or EAS when mailbox database is removed
  • This update also includes new daylight saving time (DST) updates for Exchange Server 2013.

 

Some Items For Consideration

As with previous CUs, CU6 follows the new servicing paradigmthat was previously discussed on the blog.  The CU6 package can be used to perform a new installation, or to upgrade an existing Exchange Server 2013 installation to CU6.  You do not need to install Cumulative Update 1 or 2 for Exchange Server 2013 when you are installing CU6.  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.

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

CU6 contains AD Schema updates – please test and plan accordingly!

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

 

Can You Help Us?  -- Yes !

If you would like to have Microsoft Premier Field Engineering (PFE) visit your company and assist with the topic(s) presented in this blog post, then please contact your Microsoft Premier Technical Account Manager (TAM) for more information on scheduling and our varied offerings!

If you are not currently benefiting from Microsoft Premier support and you’d like more information about Premier, please email the appropriate contact below, and tell them you how you got introduced!

US

Canada

For all other areas please use the US contact point.





Comments
  • Thanks Rhoderick, the first picture is not showing :-)

  • Hi Ed - I can see the pic on my laptop, phone and a couple of other machines (the latter are not signed in to the profile system so are anonymous).

    What do other folks see please?

    Cheers,
    Rhoderick

  • Hi, i can see the picture. Greetz, Markus

  • I just feel that your comment "Please enjoy the update responsibly!" is a bit perplexing. How could only possibly overdose or not enjoy the update responsibly?

    How an earth would you expect one to "Abuse" or "misuse" this?

    Please elaborate further

    One confused Exchange 2013 Administrator

    Kind Regards,
    Nah mate

  • @ Mr Mate!

    That comment is in there as I've had to deal with multiple customers not testing update(s) at all and on the day of release applying them to production servers. There was no consideration for testing interoperability with third party applications and services let alone native Exchange & Outlook functionality.

    All update need proper planning, testing and rollout. Exchange is no exception.

    Cheers,
    Rhoderick

    PS love the usage of "one" in your comment!

  • My domain test lab has one exchange 2003 on server 2003 domain functional level is 2003, .
    In the domain I have 2 DC that are server 2008 with active directory.
    For the last 2 weeks I have been trying to install exchange 2013 on 2012 server R2 and it keeps failing at the same point of the installation checking all prerequisites.
    Getting many errors mostly pointing to permission, the user that im using to do the install has schema & enterprise admin group permission but regardless of what I have done nothing works to get me past this.
    Below are some of the errors that Im getting.
    I need to get this project done ASAP because of serious problem with the 2003 exchange in the lvie domnain.

    I have followed the TechNet step by step to do the install for 2012 server but not for R2?
    Any help is appreciated.



    Error:
    The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx

    Error:
    You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx

    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

  • Hi Dave
    Did you use in the Windows 2012 R2 in a elevated prompt:

    setup /PrepareSchema /IacceptExchangeServerLicenseTerms
    setup /PrepareAD /IAcceptExchangeServerLicenseTerms

    Before the Exchange gui installation?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Post Comment Fixer