Microsoft has released Cumulative Update 6 for Exchange Server 2013. From the Microsoft Exchange Team blog:
CU6 represents the continuation of our Exchange 2013 servicing and builds upon Exchange 2013 CU5. The release includes fixes for customer reported issues, minor product enhancements and previously released security bulletins. A complete list of customer reported issues resolved in Exchange 2013 CU6 can be found in KB 2961810. Customers running any previous release of Exchange 2013 can move directly to CU6 today. Customers deploying Exchange 2013 for the first time may skip previous releases and start their deployment with CU6 as well.
CU6 delivers several important updates for public folder scale (now supports up to 100k folders instead of 10k) and behavior. These changes are detailed here. Also includes is the fix for the Subtask CheckPrereqs execution failed bug in the Hybrid Connectivity Wizard. Customers who have already deployed the interim update for this bug do not need to uninstall the IU before applying CU6. A list of the issues fixed in Exchange Server 2013 CU6 is available here. Updates of interest include:
- You cannot access the archive mailbox of a delegated user after enabling MAPI over HTTP
- Mail-enabled public folder accepts email messages from unauthorized users in an Exchange Server 2013 environment
- Users cannot access mailboxes in OWA or EAS when mailbox database is removed
Cumulative Update 6 is available for download here. For deployment steps refer to installing cumulative updates for Exchange Server 2013.
Issues/Recommendation:
- Exchange Server 2013-only environments – no reported issues, non-critical update, test thoroughly or wait and see.
- Exchange Server 2013/Office 365 Hybrid – important update required, refer to this article.
- Exchange Server 2013/2010 co-existence – no reported issues, non-critical update, test thoroughly or wait and see.
- Exchange Server 2013/2007 co-existence, important update required.
Related coverage:
- Exchange 2013 Cumulative Update 6 begins to address public folder scalability by Tony Redmond
- Important Update for Database Crashes in an Exchange Server 2013 Cumulative Update 6 and Exchange Server 2007 Co-Existence Environment
- Microsoft manages to ship yet another broken Cumulative Update by Michael van Horenbeeck
- Hybrid EAC & Ex2007 issues in Ex2013 CU6 by Michel de Rooij
- Don’t Deploy Exchange 2013 CU6 If You’re a Hybrid Customer by Jeff Guillet
- Exchange 2013 CU6 hybrid and co-existence bugs cause administrators to despair by Tony Redmond
Hi Paul,
I’ve noticed that when installing CU6 for Exchange 2013, the following happens:
– a new internet receive connector exists with remoteip range set to 0.0.0.0-255.255.255.255, local IP specified for the server, custom FQDN, anonymous ticked.
– installation of CU6 spits out an error saying you cannot have two receive connectors with same remoteip ranges or similar ports (to overcome this error I had to change the remoteip range of new internet connector to a random number and change the port it was listening on to port 26. This is described in the following article:
http://exchangeshare.wordpress.com/2014/07/14/exchange-2013-setup-error-a-receive-connector-must-have-a-unique-combination-of-a-local-ip-address-port-bindings-and-remote-ip-address-ranges/
Is this a bug? Should I be able to create a new internet receive connector without running into IP addressing issues? The original internet receive connector out of the box was left intact, but anonymous was removed, or should I not be doing things this way?
Thanks heaps.
Why did you modify the default connector?
Just a little notice: Your link to the download is faulty, pointing to hhttp://www.microsoft.com/downloads/details.aspx?FamilyID=781aecec-5b07-49db-842a-0aafbd78c4a8
The right address is http://www.microsoft.com/downloads/details.aspx?FamilyID=781aecec-5b07-49db-842a-0aafbd78c4a8 (one less ‘h’ in http) 😉
Thanks, fixed it 🙂
So nice of you to point out the mistake 🙂