Exchange 2013 RTM CU1 Status
Published Mar 25 2013 10:56 AM 18.1K Views
Microsoft

Originally, we stated we would deliver Exchange 2013 RTM Cumulative Update 1 (CU1) by the end of this quarter.  Unfortunately, we are not going to meet that goal. We know that many of you will be disappointed as a result of this statement. We understand your pain, however, the decision to delay is due to an issue we found in our final test pass coupled with feedback from members within our Technology Adoption Program community.

Specifically, we found an issue with Exchange 2010 coexistence. The issue actually had an easy workaround, but we made a decision; instead of burdening you with a configuration change on all of your Exchange 2010 Client Access servers, we decided to take a code change in Exchange 2013 and solve the problem so that you will not have to make any additional configuration changes. Given that the goal of CU1 is to enable coexistence with legacy versions of Exchange, we felt this was the right decision; after all, we want to ensure that your upgrade to Exchange 2013 and your coexistence period goes as smooth as possible.

As previously mentioned, Exchange 2013's update strategy is different from previous releases; we are uncoupling security updates and reducing the number of updates we release. In addition to those changes, we will continue to evaluate issues as they are identified during development (even during the final test pass) and if we determine that the vast majority of on-premises customers are affected, we will do everything we can to mitigate the issue prior to release, even if that means delaying the release.

We regret the impact that this delay has on our customers, and as always, we continue to identify ways to better serve your needs through our regular servicing releases. The release date for Exchange 2013 RTM CU1 is currently planned for April 2nd. We will let you know if that date changes, as well as, post an announcement when the download is live.

Ross Smith IV
Principal Program Manager
Exchange Customer Experience

83 Comments
Not applicable

We can still wait :)

Not applicable

Don't forget to look at PF migration. Specially for organization spread globally with multiple servers with low bandwidth site. I gave a script solution to your tier4 engg, how to control the PF storm rather stopping at org level or disabling the PF replication.

Not applicable

Keep up the good work.  We'll check back April 2.

Not applicable

I'm just glad we have a date. One more week doesn't hurt. Great job guys

Not applicable

We hope that the mapi bug will be fixed... We're losing a lot of e-mail :(

Not applicable

With all the crummy half-baked RTM and updates released lately, it is certainly refreshing to hear this news. I'll gladly wait another week rather than have to go through another twice-recalled rollup fiasco again. So, kudos to the Exchange team for having the big ones to just come right out and tell us the not really so bad news. Hopefully on April 2nd we'll finally (and I do emphasize FINALLY) be able to have a usable and finished Exchange 2013 server we can actually start testing and deploy with our Exchange 2010 setups. Yea!

Not applicable

Can we expect an updated 2013 Sizing Calculator as well?

Not applicable

@Tomlinsc - Yes, we will be releasing an Exchange 2013 Role Requirements Calculator, however, I do not have a release date for you yet.  I can tell you we are actively working on it.

Ross

Not applicable

Thanks for the update. I'm not disappointed - you are just acting professionally.

Not applicable

Any date for Exchange 2007 coëxistance upgrade?

Not applicable
Not applicable

Thanks for delaying and focusing on quality and simplification. Also thanks for the date, but quality should still come 1st.

Not applicable

As SP3 was heralded as the product level for Exchange 2010/2013 coexistence, I applaud the decision to move required changes to Exchange 2013, as introducing another update for the 2010 platform might require additional test and acceptance tracks for that change.

Not applicable

Disappointing but not surprising.  Keep up the good work, Ross - appreciate the update.

Not applicable

This is a good new for us Exchange On-Premises customers, Microsoft is talking Exchange On-Premises CUs seriously.

Thanks Exchange Team.

Not applicable

Wow, a 2 day delay is pretty good :)

I know we've all been waiting (I haven't been able to test Exchange 2013 in the lab) but keep up the good work guys, and thanks for the info!

Not applicable

just be thankful that the window has narrowed..  first from "sometime in 2013" to "Q1 2013" ..  now to April 2.   i dont really care that its delayed.. just nice to be able to plan my week now..

Not applicable

Not too suprising when I see in my lab coexistence between E2010 SP3 and E2013 RTM working well for most part except for passing correct Authentication settings with Autodiscover to my Outlook clients (got the issue from 2007 to 2013). Typically, my analysis is that _because_ Exchange 2013 is Mapi/Http only then the Autodiscover process send an empty/anonymous Mapi/Rpc and therefore the Outlook client is no longer in 'Negotiate/Kerberos' (the default) and when dealing with connectivity to Exchange 2010 coexisting services (ex: Public Folders or just a Rpc Client Access Array) this goes 'kaboom' :) - the only workaround I found was to reconfigure the Mapi/Rpc authentication scheme to Nego and this worked, but indeed not a viable approach :\

Let's cross finger that CU1 will provide all that is needed to coexist properly with minimum impact everywhere (including clients ^^).

Not applicable

I can't argue with your reasoning.  Can you go into any detail abou the issue that you found?

Not applicable

Well done team, thanks for making everything more seamless for us!

Not applicable

What about the E2K13 sizing tool? Thks

Not applicable

I'm surprised at all the positive feedback since Microsoft has completely mishandled this situation.  Did we forget that it's been almost 6 months since the release of Exchange 2013 and really nobody can use it?  How about actually writing good code the first time and then you won't have to keep just saying "just one more week and it MAY work".

Not applicable

Nice decision. Better its delayed rather having issues and investing more time troubleshooting it. All the best team...:) We are waiting.

Not applicable

@Exchange Blogger - I have been highly critical of the whole ordeal but at this point, better to have a workable product than have it rushed to meet a deadline.  It's pretty clear that the whole Exchange 2013 debacle was due to an artificial deadline imposed so that the release could meet the rest of the Wave 15 timeline, and Exchange simply wasn't baked yet.  Here's hoping that with CU1, it will be!

Not applicable

Thank you Exchange Team for testing this again and again before giving it to us Exchange On-Premises customers.

Not applicable

Based on how long this has been in development, how long 2013 has been out, etc, and then to announce a couple of days prior to release that a coexistence bug has been found, and then that you plan to fix it over Easter weekend, doesn't instill a giant amount of confidence in rolling this out to my clients.  I have several signed scopes of work waiting on this for coexistence/migration, and I'm not getting the "warm fuzzies" leading up to release.  Think I'll wait a couple of weeks to see if this explodes anyone's exchange org before I take the plunge.

Not applicable

Wise decision !

Not applicable

what about all the documentation on upgrading and coexistence?

Not applicable

Thank you for the update and clear information - this is the right approach to restore confidence in a process that has been failing of late.

Not applicable

Well, who cares?

Not applicable

Are there schema changes in E2013 cu1 as against e2013 release?

Not applicable

Thanks for the update, nice to have an approximate release date.Looking forward to it.

Not applicable

Have Anyone succsessfully Migrate PF from Exchnage 2010SP3 Release to Exchange 2013 RTM? The Step by Step Guide from the Technet Website doesn't work.

technet.microsoft.com/.../jj150486(v=exchg.150).aspx

Get-PublicFolder -Recurse | ConvertTo-CSV C:PFMigrationEx2010_PFStructure.csv

Get-PublicFolder -Recurse | Get-PublicFolderStatistics | ConvertTo-CSV C:PFMigrationEx2010_PFStatistics.csv

Get-PublicFolder -GetChildren | Get-PublicFolderClientPermission | Select-Object Identity,User -ExpandProperty AccessRights | ConvertTo-CSV C:PFMigrationEx2010_PFPerms.csv

I get n syntax Error or Pipelining Error

Have someone a better Step-by-Step Guide to Migrate PF ??

THX a lot for your help

Not applicable

I think a very good decision!! better release good software and wait longer, then release sh*tty software with stupid bugs and during upgrade a break down of your environment.

good work guys, we will have patience.

Regards,

Leon

Not applicable

@Steve, yes there will be a schema update in CU1.

Not applicable

Finally a word from Microsoft we have been waiting...

I take your words ROSS!

Not applicable

(posted once already but maybe it did not work?)

@Brian Day, Thanks for the info, had expected that but it helps to know this for sure

@MSFT, Thanks for the update.  It's much appreciated.  I have also a hard timetable to meet! The more you can keep us "out here" in the loop, the easier you make our work.  Please keep it up! Also, the quicker you can provide content for the various holding pages in technet, the better.  Cheers, Steve

Not applicable

@Anker: Coexistence & upgrade documentation is currently planned for April 3rd.

Not applicable

finally we get an update to this issue and a release date. Hope it will work well for all of us.

Not applicable

Good transparency, guys. And the comments.

Not applicable

Good to have a date.  I have plenty of customers (via http://emailmigrations.com) lining up to deploy Exchange 2013 CU1 into their Exchange 2010 SP3 Organizations.  

Not applicable

Benoit Boudeville: I get this same issue. After using Autodiscover to connect to mailbox, the MAPI Outlook Security settings are set to Anonymous Auth, the Outlook Anywhere Connection settings are set correct.

Public Folders can't be accessed, until I manually change the MAPI security to Negotiate. I thought there was something I need to change in Ex 2007, but not sure at this stage.?

Not applicable

Looking forward for Exchange 2013 Mailbox Calculator and Migration documents

Not applicable

I hope we will get CU1 on 2nd April 2013.

Not applicable

Thank you for the update.  I look forward to the "real" release of Exchange 2013 (the one that can be installed by the vast majority of your customers)

Not applicable

@Benoit and @Ryan I am performing some tests between 2007 and 2013 rtm. Could you please tell me where can I change MAPI/Rpc authentication scheme to Negotiate?

Not applicable

Please fix the DLP issues..............it was sold to us as working and great reason to move to new 365.......it is 50-50 chance of it working.  At least let us know when this function will be available.

Not applicable

Don't worry about it Ross - you're only missing the deadline by a couple of days anyway. I would prefer that you do proper testing on an update before releasing it and if the delay means that we won't need to make changes for co-existence then it's worth it.

Not applicable

Hi,

  will it be possible to upgrade Exchange 2010 sp3 to 2013 cu1 on the same machine?

Not applicable

Thanks for the update on CU1.

I look forward to the release of CU1 primarily so that the incessant whining in the comments section of this blog about the integration of 2013 with earlier releases can stop and those that are so inclined can move onto whining about new topics.

Version history
Last update:
‎Jul 01 2019 04:12 PM
Updated by: