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
Update 13-1-2015: Adding issue noted with Enterprise Vault. This is discussed in KB 3011579.
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.
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!
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.
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!
For all other areas please use the US contact point.
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?
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
@ 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.
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.
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
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
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
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
Did you use in the Windows 2012 R2 in a elevated prompt:
setup /PrepareSchema /IacceptExchangeServerLicenseTerms
setup /PrepareAD /IAcceptExchangeServerLicenseTerms
Before the Exchange gui installation?
The default time zone.
After implementing this CU, When users first log on to OWA they find a screen which is asking them to select the "Language and Time Zone". Language is default set (English), But Timezone is not set by default. Can somebody help setting the default time zone??
because that will mislead the users to set it wrong.
Hello, when you say "Note that customised configuration files are overwritten on installation" what types of customisation?