Exchange Server 2013 Service Pack 1 Coming in Early 2014

Today on the Office blog we announced that service pack 1 for the 2013 set of products including Office, SharePoint and Exchange will be released early next year. We know our Exchange customers have been looking for confirmation of the release but also have a desire for an early look at what's coming with Exchange Server 2013 Service Pack 1 (SP1). So let's have a first look a few things you can expect to see in SP1. But wait… we haven’t released CU3 – well, news about CU3 is imminent - stay tuned for more information about CU3 coming very soon.

In this post we are highlighting a few of the notable improvements to be included in SP1. This isn't an all-inclusive list, so stay tuned for additional details as we approach release.

  • Windows Server 2012 R2 Support First answering one the most common questions since the release of Windows Server 2012 R2. Exchange 2013 SP1 will add Windows Server 2012 R2 as a supported operating system for Exchange Server 2013 with SP1. Let your planning begin.
  • S/MIME support for OWA Support for S/MIME in OWA will be brought back in SP1. With SP1 customers will have S/MIME support across Outlook, Exchange ActiveSync clients, and OWA.
  • Edge Transport Server Role The Edge Transport server role for Exchange Server 2013 will be available with SP1.
  • Fixes and Improvements Of course, SP1 will include fixes and improvements in areas you've helped us identity. SP1 is the first service pack issued in the new Exchange Server cumulative update release model - thus SP1 is essentially CU4. The installation of SP1 will follow the same process as the prior Exchange 2013 CU releases. SP1 will include all fixes included in previously released cumulative updates for Exchange 2013.

SP1 will require customers to update their Active Directory schema - customers should assume this requirement for all Exchange Server 2013 updates. Plan for this required update to quickly take advantage SP1 updates. Active Directory Schema updates for Exchange are additive and always backwards compatible with previous releases and versions.

On behalf of the Exchange Product Group, thanks again for your continued support. As always, let us know what you think!

Brian Shiers
Exchange Technical Product Manager

Comments (123)
  1. Anonymous says:

    I am running ex2013 latest cu and fixes on a server 2012 R2 with the highest domain functional level on DC’s!!

    not a problem!

    Spam filtering is terrible. and the rest others have complained enough about already.

    just for those who wanted to know if it would work.

  2. Anonymous says:

    HI Guys,

    Some news about Exchange 2013 Sp1 release date ?

  3. Anonymous says:

    Nice Playaz

  4. Anonymous says:

    Would be really good to have a way to set the image size pushed in the thumbnail AD attribute.
    We have some other application that are using the thumbnail attribute picture from AD and expect a 96x96px picture, or even 120×120.
    Thanks !

  5. Anonymous says:

    Can someone from the team explain why Auto Attendant menu navigation was changed in Ex2013 to only allow as many digits are in the dial plan? In Exchange 2010 we used 11 digits (the full DID) there because it made mapping to users easy regardless of Dial Plan/matching. Now that we are limited to 4 digits we are having to recreate every single Lync dial plan to match the fqdn of the Exchange dial plan, and then create normalization rules for every area code and prefix we have. Argh!

  6. Anonymous says:

    Exchange 2013 cu2 works fine on Server 2012r2 we already 3 months, 1500 mailboxes.

  7. Brian Shiers [MSFT] says:

    @M. Kaelin; @waiting for godot; @ Avin; @Luca @ KNE; @Exch Admin; @Earl; @Service Pack 1 Release; @Early 2014?; @Mike; @Ridiculous; @Michael Blaser; @Clint Boessen [MVP]; @SP1 Fan; @Mike We appreciate everyone’s enthusiasm to get SP1, but we won’t be providing
    a more specific timeline in advance of the SP1 release. We will announce availability on the EHLO blog as soon as it becomes available early this year.

  8. Exchange TEAM,

    Any chance that you could extend your functionality around ABP.
    There have been some great improvements, but for hosters somthing important is still missing.
    For example you gave us “AddressBookPolicyRoutingEnabled” to prevent name resolution. Im sure you can also build something like that to deal with the issues around internal/external OOF – AND the issue around Mail Tips.
    I know about custom transport agents, but that, I think, is not THE great solution. I believe that this functionality shuold be IN the product ???

  9. Anonymous says:


  10. Anonymous says:

    Hi, guys. I suppose, you need more tools in ECP to manage mail server. Now 2/3 of tasks i do in EMS – this is not good. It’s not a Unix – this is Windows. For Example: – How to see users, connected now ? – EMS – How to import-export user mailboxes ? –
    EMS – How to manage Antispam defense ? – EMS – How to repair EDB file ? – EMS, EMS. EMS … Guys, i dont like Unix cause command promt. I like Windows with buttons and "windows", and look at you window – 2014 year already … voice recognition and more cool
    stuff … but with Exchange 2013 i returned 20 years ago – back to the command promt. Sure, we need EMS sometime, bt, i suppose, most of regular tasks we need to do through ECP. Thanks.

  11. Nino Bilic says:

    Folks, thanks for asking and patiently waiting. When we have SP1 related news, it’ll be on the blog on the front page. Things look good so far, but we will not announce anything specific until we are confident and ready to release.

  12. Brian Shiers [MSFT] says:

    @Mika Vistab We continually work with L&EDPS programs to maintain updated content – refer to the program directly for planned content updates. If you have specific content requests for the program refer the contacts available @
    to share your requests

  13. Anonymous says:

    Quite upsetting how this has gone – would have expected MS to be on top of this, especially with the release of the new OS. Going to use alternatives now, sorry MS. You just lost my business.

  14. Anonymous says:

    Still waiting for Exchange 2013-SP1.

    We have a site running on Server 2012 R2 Active Directory, we need to install Exchange 2013 on one of their servers.

    Give us at least when we can expect the SP1……

  15. Anonymous says:

    Ok, it’s early 2014, so when is SP1 going to be released? Thanks.

  16. Anonymous says:

    PowerShell cmdlets Get-MailboxSentItemsConfiguration and Set-MailboxSentItemsConfiguration were available in Exchange 2010, but they are not in Exchange 2013. This is a problem and no real solution is available. The alternative DelegateSentItemsStyle registry entry is not a real solution and is not working properly.

    PLEASE give us powerShell cmdlets MailboxSentItemsConfiguration in Exchange 2013 SP1 !!!!!!!

  17. Tom Phillips says:

    So what is considered "early"?  We need the R2 support as we skipped 2012 as a base image in favor of R2.  We have our Exchange upgrade project which puts server OS installs at the end of Jan 2014…..

    thanks for all the hard work to get us here….it is appreciated.

  18. Bob Hyatt says:

    This is a GREAT news for Exchange 2013 On-Premises customers worldwide :-)

  19. Bharat Suneja [MSFT] says:

    @Bob: Thanks for the feedback from on-premises customers! :)

  20. Brian Shiers [MSFT] says:

    @Tom Phillips: We can't provide a more specific answer at this point as the top priority is quality and we don't want set incorrect expecations.   Thanks for your feedback.

  21. David says:

    Thank you for addressing the SP1 question.  We are looking forward to CU3.  Can you please include fix notes so that we will know which issues are addressed with each cumulative update?  It will help us in deciding the timing the rollout of each patch.  There is nothing more frustrating than planning and deploying only to find out that our problems persist since we had no idea if a particular CU even addressed our issues.

  22. Bharat Suneja [MSFT] says:

    @David: We include the list of issues fixed in the accompanying support article (KBA). We can't share it before an update is released, sorry!

  23. Miha Pecnik says:

    Since Exchange is one of the core products, the cycle of releasing CU's, SP's that provide support for the newest OS's should be more in line with Windows Server releases. Much like System Center products. Still welcome news that R2 support is coming.

  24. Matt says:

    Any mention of "Show Exchange Management Shell Command" or "View Exchange Management Shell Command Log" functionality in EAC with SP1?

  25. Brian Shiers [MSFT] says:

    @Matt: This post provides a view of a few of the SP1 updates we are committed to shipping with SP1 – we can't provide a list of additional updates that will be included in SP1 at this time.  More details of course will be provided with the SP1 release.  Thanks for your feedback.

  26. ravikumar says:

    Do we get Powershell 4.0 support for Exchange after this Service pack, As we know it is not supported till date with Exchange 2013, same as with powershell 3.0 for Exchange 2010

  27. Nathan says:

    This is real Fun. Recent Launch of Exchange 2013 is a real Pain. Half of the features working in 2010 doesn't work in 2013 any more. we have spent tons of hours with with support teams to fix the issues, unwanted

    head aches and time waste bcs they don't fix and end users are crying.

    Instead of fixing the prodcut issues first, what's the hurry for SP1. something is really worng the way these releases are happening.

  28. Steve says:

    Commenting on David's comment, why would a specific list of fixes be published for Service Pack and not a Cumulative Update?  On-Premise customers need to know what is specifically being fixed in CU's , not having a fix list is pretty sad.

  29. Berndk says:

    CU3? We have the fourth quarter of the year!!! CUs were announced quarterly.  SP1 in "early 2014"????? And I shall let you know what I think? Better not.

  30. Bharat Suneja [MSFT] says:

    @Steve: Please note, the response was to releasing a list of included fixes *before* the update is released. 

    " We include the list of issues fixed in the accompanying support article (KBA). We can’t share it before an update is released, sorry!"

  31. Georgi Ivanov says:

    What about desired state configuration resource for exchange ?

  32. Simon says:

    Will Anti-Spam be supported on regular single-box installations?

  33. PrivateFolder says:

    when will the hierarchy of a mailbox folder and public folder be able to be restored from recover deleted items/dumpster?

    I cant believe this feature is not "enabled"

    how can we run restores using single item restore when we cant restore a users folder:)?

    need to restore the whole mailbox from backup for one user folder(meaning cannot go to Hugh databases and mailboxes)


  34. Bharat Suneja [MSFT] says:

    @PrivateFolder: Thanks for the feedback regarding lack of ability to restore a soft deleted item (using Single Item Recovery or Recover Deleted Items) to its original folder. The original folder info is not stored with the deleted item, so it's not something that can be enabled via a config change.

    While this is being considered, would you restore an entire mailbox to ensure some deleted items are recovered back to their original folder?

  35. Bharat Suneja [MSFT] says:

    @Georgi Ivanov: Can you provide more info? Thanks!

  36. Steve says:

    I've never seen a list of bug fixes contained in a Cumulative Update for Exchange 2013.  If they exists for CU1 & Cu2 then please share the link? Or is MS changing its tune with CU3 to include the bugs (that we have found) that will be fixed?

  37. . says:


    KB article for Exchange 2013 cu2:…/2859928

    KB article for Exchange 2013 cu1:…/2816900

    Where is the "list of issues fixed" on either of those links?

  38. Durval Ramos says:

    Gold News. Exchange 2013 better with SP1

  39. Charles Derber says:

    Looking forward to see whats new in Exchange 2013 Edge Role Architecture and its features :)

  40. Bharat Suneja [MSFT] says:

    @Steve: You're right. Apparently I was still in Exchange 2007/2010 RU mode earlier, where corresponding KBAs did include the list of issues that customers reported and were fixed in those releases. Both the Exchange 2010 CUs do not have the list. I will update when I have more to share, either in this thread (or perhaps an upcoming post).

  41. EdgeRole says:

    Will we have a full architecture and features available before SP1 for the Edge role so it helps in planning for deployment and migrations? When in the near future can we expect this?

  42. Bharat Suneja [MSFT] says:

    @Steve, @David and others: An update on this – the list of fixes for customer-reported issues will be included in the Exchange 2013 CU3 KBA and SP1 documentation will also make this easy to track. 

    We know the lists were not generated for Exchange 2013
    and are attempting to go back and update those KBAs. But the list of fixes will be included from CU3 onwards. Sorry for the inconvenience and thanks again for the feedback.

  43. Georgi Ivanov says:

    @Bharat Suneja,

    One of the great new feature in PoweShell 4.0 is DSC, where you can use build-in DSC Resources or create your own to declare the configuration of a system.

    As I`m aware the Exchange team is pretty innovative with PowerShell, so I was thinking what about leveraging this PS DSC feature to declare the exchange configuration, so it can be auto-remediated on regular basis.

    It will be extremely useful in large deployments or multi-tenant deployments in *-cloud environments.

    It will be also very easy to migrate the configuration from DEV to Test and to Prod Environments.

    And also as some of the settings are reverted when you install new CUs, they will be auto-remediated on regular basis.

  44. Rick Eveleigh says:

    Is Exchange 2013 supported now on Windows Server 2012 running in a domain with only Server 2012 R2 DCs?

  45. Feels like a fluffy post to me that is just to distract from the 'Road ahead' post and all of the comments it generated.

    Why talk about features in SP1 when that is effectively CU4? – just concentrate on explaining CU3 and how that might help some of the poor people here trying to get things working

    I'm the Exchange architect for a very large migration piece and there are plenty of delays – seems with all of the randomness with Exchange updates and in the field pain the delay will actually be a good thing

    Looking forward to better communication

  46. Zoher Abuzar says:

    Microsoft should make up his mind, why Edge was removed in first place if its back in SP1? We moved to Iron Port (costly implementation) and now we have Edge role. Idiots.

  47. @Rick Eveleigh, we are working through the process to validate Windows Server 2012 R2 Domain Controller support with Exchange at this time. Once everything is ready we'll update the supportability matrix at with that information.

  48. Berndk says:

    " ….. we are working through the process to validate Windows Server 2012 R2 Domain Controller support with Exchange at this time" Ah, so the release of Windows Server 2012 R2 was a surprise to the Exchange Team and fully unexpected, therefore the delay in supporting Exchange 2013 on 2012 R2. So the developers of Server 2012 and the developers of Exchange must be in two complete different companies ….

    Come on guys, Server 2012 R2 wasn't developed in a few days so you had plenty of time for a CU supporting Exchange 2013 on it!!!!

    Do you think we believe in Santa Clause and Earth is a disc?

  49. asfasd aerwgteg eqrgbadfbadf getsh etrwegawgasgdoasjgop uasiha;iogh ahgio ogiaog aiog ioahgioasj g j says:


    "We know the lists were not generated for Exchange 2013 CU1 & CU2 and are attempting to go back and update those KBAs. But the list of fixes will be included from CU3 onwards. Sorry for the inconvenience and thanks again for the feedback."

    So, you fibbed to us about the information being in the kb articles, even after numerous people have brought this to your attention. Then, when you have egg all over your face, you are now "attempting" to go back and update them?

    When you say "attempting" what does that mean? To me, that means that you probably won't fix anything. You either fix it or you don't. "Attempting" to fix something means, you probably are not really going to fix it in the end or it will be done half-assed, which is the current state of things as well.

  50. Bharat Suneja [MSFT] says:

    @Zoher: We’ve previously stated that the Edge Transport server role is not available in Exchange 2013 at RTM or that it’s not available yet (as opposed to the role being discontinued altogether). Workarounds have also been suggested, including using an Exchange
    2010/2007 Edge Transport server or FOPE.

    From one comment from July 2012 when
    Exchange 2013 was announced

    @G: Exchange Server 2013 doesn’t yet have an Edge transport server role, but you can continue to use Exchange 2010 Edge servers until we deliver an Edge transport server role in a future release. You can also use FOPE for protecting inbound/outboud mail.

    Use an Edge Transport Server in Exchange 2013
    in Exchange 2013 documentation:

    The Edge Transport server is not currently available in Microsoft Exchange Server 2013. However, you can continue to use existing Exchange Server 2007 or Exchange Server 2010 Edge Transport servers that you have deployed in your perimeter network. Or, you
    can install a new Exchange 2007 or Exchange 2010 Edge Transport server in your perimeter network for a new or upgraded Exchange 2013 organization.

    Also note, in
    What’s Discontinued in Exchange 2013
    > Architecture, the Hub Transport and Unified Messaging server roles are listed as discontinued – the Edge Transport server role is not.

  51. Bharat Suneja [MSFT] says:

    @Georgi: Thanks for the great feedback, will pass it on to the team.

  52. Bharat Suneja [MSFT] says:


    >>Come on guys, Server 2012 R2 wasn't developed in a few days so you had plenty of time for a CU supporting Exchange 2013 on it!!!!

    As stated in previous comments, Exchange server support for a new Windows Server version is typically included in the next service pack. Windows Server 2012 R2 support is included in Exchange 2013 SP1.

  53. Phil says:


    we need extremely a hotfix for these two EAS sync. errors with iOS

    Microsoft: [REG:113111310943037] Callback:IPhone Calendar Sync Problem with Outlook  Initial Response

    (Microsoft: REG:113051510439694] Callback:iPhone Calendar Sync Problem with recurring item (was sadly closed!))


    Apple Support: [411633063] Sync issue between Ios and MS Exchange

    very briefly description:

    * Updates and moves of recurring events (!with a booked resource like a meeting room!) are not sync. correctly to iPhones.

    It does NOT work with:

    * Exchange 2010 Sp3 Ru2 and Outlook with *Cache Mode* (doesn't matter Office 2010 Sp2 or 2013)

    * iPhone with push notification (until iOS 6.x – 7.0.x)

    It works with:

    * Exchange 2010 Sp3 Ru2 and Outlook (2010/2013) in Online Mode!

    * or Exchange 2013 Cu2 and Outlook with *Cache Mode* !

    * or with OWA (2010 / 2013)

    * or an iPhone with disabled Push (set to manually)

    Since one year, we are a plaything between MS and Apple :-(

    Please help us and escalate it internally!



  54. Clint says:

    Disappointing to hear nothing on plans for server core support. With the great 2012 remote management features, I really should not need local GUIs on my Exchange server anymore.

  55. LucidFlyer says:

    Is there any Exchange 2013-related Edge info available?

  56. Bharat Suneja [MSFT] says:

    @LucidFlyer: No. It's inclusion in SP1 has been (formally) announced in this post yesterday.

  57. Steve says:


    Thanks for the info on the publishing of bug fixes in CU's & Svc Packs!

  58. PrivateFolder says:

      Bharat Suneja

    known issue(that its not stored, that's the main issue it was in the past)

    yes, we have no choice that's what we are doing

    but we want to go to exchange 2013 with bigh mailboxes(5gb) plus 15-20Gb archive but how can we when each database will be big now(at least 1tera,multiple copies and all) and we have to restore 1tera atleast for restoring one folder that the user deleted(from pf mailbox or mailbox) its hard enough to backup all the data on exchange 2010:)

    on another note:)

    is there away to "maintain" archives?

    for example I want to move all items in all folder after 365 days to archive(no problem here, working fine)

    but I also have a requirement to remove all items from archive mailbox older than 5 years(have no clue how to achieve that, will using same kind of policies on the mailbox level work?

    Thanks in advance

  59. Bharat Suneja [MSFT] says:

    @PrivateFolder: Use a
    Retention Policy
    to move items to the archive in 1 year, and delete items in 5 years (or if you meant 5 years after moving to archive, then total of 6 years). This will delete items in 5 (or 6, depending on which option you choose) years.

  60. Exchange 2013 Support Active Directory 2012 R2? says:


    Perhaps I did not see it. But will CU3 Support Active Directory 2012 R2? Also at the Domain and Forest Level?

    Or do we have to wait for SP1?

    We have interest in upgrading as soon as possible to Active Directory 2012 R2.



  61. 2013denier says:

    @Zoher Abuzar: We switched to Ironport long time ago. Best decision ever.

  62. Gordon says:

    On what browsers/platforms will S/MIME in OWA be supported?  Specifically, will Firefox on Linux be able to use S/MIME in OWA?

  63. Brian Shiers [MSFT] says:

    @Gordon: S/MIME support in Exchange Server 2013 SP1 will require the user’s browser to be Microsoft Internet Explorer 9 or greater to use this feature.  We understand some customers may desire support for other platforms and we are looking at the best way to bring this support to other platforms in the future – but nothing we can share now.

  64. Frank says:

    Good news to hear about the release of SP1 but please release information on CU3 very soon. We are currently doing a 5000 user migration from Lotus Domino to Exchange 2013 CU2 and it is so full of issues that sometimes I spend 2 days a week just looking after it. We only have 100 users on it so far!

    Keep up the good work, I definitely would appreciate the appearance of fix lists for CUs. That is very very important for many customers including us.

  65. HotFix says:

    @  Bharat Suneja – yes today we are forced to restore an entire database to restore an entire mailbox just to get back the folder hierarchy. This is extremely frustrating to us as it is about the only reason we keep traditional backups. Folder hierarchy was maintained in the old Exchange 2007 dumpster, and we understand the massive change in Dumpster 2.0, but maintaining the folder hierarchy in deleted item recovery is something that people have been asking for since Exchange 2010 RTM'ed and they realized it was now missing.

    Please help us move away from traditional backups by adding the information in Dumpster 2.0 as to where the item was originally deleted from so we have chance to put the mailbox back the way it was w/o needing a full database restore.

  66. @Hotfix, have you investigated deploying a lag copy as a means of performing item restoration with folder paths? A lag copy can provide up to two weeks of time where (if the user knows what timeframe the delete happened) you can make a copy the lag copy, mount the copy as a restoration DB, and then export the content with folder paths intact. Spin up a thread on the TechNet forums if you'd like more info.

  67. pesospesos says:

    @Brian, the lag copy – if I understand correctly – does not really solve the issue.  The only step of the ridiculous process we have to go through to restore a mailbox that the lag copy avoids is the restore of the database file from backups.  We still have to do the recovery DB, export the PST, somehow get the user the PST, have them dig through it to get what they want, then tear it all down again.

    The lag copy simply saves a bit of time (most of which is just waiting for the restore itself, not active working time) – and it means that we have the space of the entire database taken up at all times instead of just during a restore event.

    It really is ridiculous not to have proper item-level restore in a product as advanced as Exchange – my clients are continually baffled when I explain to them the way it works currently.

  68. @pesos, it is merely an option to consider at this time. The other tangible benefits are not using up all of the space on the backup system for each snapshot or tape full of data, dealing with backup agents, waiting for restores as you said, and you can skip export to PST and inject the content back to the mailbox if the user gives you enough information on what to restore. There are pros and cons for each option to weigh against business requirements.

    I present it as an option for customers to consider, not an 'excuse' for why the folder information is not natively recoverable from the Recoverable Items folder. The architectural changes made in Exchange 2010 to enable a suite of other options made this particular task considerably more difficult to implement. That's the honest truth and teams within Exchange are well aware of the desire to see it possible. I would also like to see the option available.

  69. dog says:

    brian – when an item is deleted, how hard can it be to simply record the original folder path along with the deleted flag? Then offer an option to either restore to a single flat folder, or back to the original mailbox path. Seems relatively simple, from a database-perspective. Can you explain to us further why this is so technically challenging?

  70. @dog, comments are sadly a terrible medium for lengthy technical discussions (TechNet forum is better). :( Suffice it to say it is a more difficult process than it appears on the surface. I know that will appear like some sort of cop-out, but I prefer to be honest even when the message is not the one people want to hear. I'd rather drink a scotch bonnet pepper smoothie than deliver unwanted news. Nobody likes giving bad news.

    The advice I give customers in these kinds of situations is that if you are a Premier Support customer the best thing you can do is work with your Technical Account Manager to file a Design Change Request (DCR) with a strong business case attached. This helps the different product teams evaluate feedback from the field and triage what areas need work against each others when there is verified evidence available to review. It's a little bit of leg-work and you may even get back a 'not accepted' response back, but each is filed and additional requests for the same thing stack up may push it over the triage bar depending on what else is being worked on. For those whom are not Premier Support customers we do share comments from here with the appropriate teams as well, but the DCR process is a bit more formalized.

    Again, this specific area is something the necessary teams are already aware of. We cannot share more than that nor make promises at this time.

  71. Barebodkin says:

    Can you please clarify about Forefront Protection for Exchange (totally on-premises, not exchange online and not forefront online), with respect to the new Exchange 2013 edge transport role.

    Currently I have Exchange 2010 edge transport role servers, running forefront protection for exchange 2010. Is there an upgrade path which would allow us to continue FPE? If not, can you please compare and contrast the anti-spam features of Exchange 2013 vs Exchange 2010 with FPE?


  72. @Barebodkin, FPE 2010 is not supported on Exchange Server 2013 so I don't expect to see it supported for install on Edge 2013, but we can't say more on Edge at this time. Your second ask sounds like a good idea for a blog article here though.

  73. George says:

    Drop of FPE in exchange 2013 is one of the issues that put on hold our migration plans. Forefront online is not much different form exchange online – emails will pass through Microsoft. As for switching to Microsoft cloud services in general, what would Microsoft say to suggestion to store their (Microsoft) corporate emails, documents, program codes, etc on Google cloud service? This is exactly what Microsoft pushes its customers to do (to store corporate data externally on 3-rd party cloud service).

  74. StevieT says:

    If for some reason we didn't want to wait for SP1, would it be possible to coexist with an Exchange 2013 CU2 running and Exchange 2013 SP1? I'm trying to come up with an upgrade plan.

    Thank you in advance,

  75. Tibor M says:

    @Brian Shiers, @MSFT if you are in lack of engineers then employ me :) i will do my best to deliver on time :)

    if not, then release CU3 finally. Our CEO is almost throwing me out of the window because YOUR product has bugs!!

  76. Good eyes, @Tibor M, posts to follow soon once content replicates.

  77. Rick Eveleigh says:

    CU3 is out but still no word on support for DCs running Server 2012 R2 or Domain Functional Level of Server 2012 R2. On the CU3 announcement comments a user says he's been running against 2012 R2 DCs with no issues but, acknowledging that @Brian Day said earlier you were validating, is there a timeframe for the supportability statement? And are you validating using CU3 or an RC of SP1? We have an imminent greenfield deployment and need to decide if the DCs are to be 2012 or 2012 R2.


  78. DontLikeIt says:

    There was a time when Microsoft supported their own products.

    At least the latest versions (and if there was a known problem, there was a big red flashlight somewhere).

    Then there was a time when you couldn't rely on that anymore.

    You had to investigate, read tons of Technet and Blog entries, ask Microsoft and so forth to get a feeling if it's worth starting with test-installations as soon as a new product arrived.

    The world has changed again.

    Nowadays you don't get any reliable information, questions to this Blog are predominantly ignored (eg support for 2012r2 DCs).

    How long do you think it will take for the last engineer to turn her back on you?

    Only after the last tree has been cut down

    Only after the last river has been poisoned

    Only after the last fish has been caught

    Then will you find that the cloud cannot be eaten.

  79. Rob Campbell says:

    Will the Edge role run on a server core platform?

  80. Fish says:

    I’m about to deploy E2013 and REALLY want it to be on 2012 R2. What happens if I just run with CU3? I see that E2013 will actually install. Any risk in simply installing it to prepare my infrastructure and don’t migrate mailboxes until it’s supported?

  81. maartenK says:

    It doesn`t say Exchange 2013 wouldn`t work on Windows Server 2012 R2. But it isn`t supported (yet). Hope Microsoft will release at least a date when the CU will come?

    Early 2014 could be long……..Januari, Fenbruari etc…..

    For now we are running it on Windows 2012 and maybe later on flip to Windows 2012 R2. Its a small transition for us. We have 275 user mailboxes.

  82. Have you tested this in an on-premise environment???

  83. mike says:

    Any updates on release date for Exchange 2013 SP1? Thanks.

  84. yoni says:

    Any News regarding the SP1 ? Where is the best place to stay tuned ?

  85. Rhys says:

    “we will not announce anything specific until we are confident and ready to release.”

    You don’t know when you’re going to release? There’s this program called Microsoft Project, see if you can get a free copy. Lack of planning kind of indicates what the SP1 is going to look like.

    Is it entirely outsourced and you just email them once a week with ‘is it done yet?’

  86. Leon says:

    I know you guys get a lot of critics, i think exchange 2013 is an improvement of exchange 2010. but please guys test the coming sp1 inside out before release, better one month more testing then a sh*tload off problems after release and stuff does not work.

    Take your time and release a great sp1! :)

  87. Anonymous says:

    Also test 2013-SP1 on the migration from Exchange 2007/2010, making sure it does not screw up the mailboxes while migrating…..

  88. SP1 Fan says:

    It’s early 2014… any date yet?

  89. D'sNotPlanters says:

    How is it that the Lync team could release a CU for Lync to support Server 2012 R2 in a timely manner? And the Exchange team is dragging their feet? SP1 for Exchange is essentially CU4, you guys have said that, so really what is taking so long?

  90. Clint Boessen [MVP] says:

    Can we have an update on SP1 release, need to deploy new Exchange 2013 environments and would like to use Windows Server 2012 R2 please.

  91. Michael Blaser says:

    We need to deploy exchange 2013 asap and want to use windows server 2012 R2.
    Are there any news around about the release date?

  92. PSS says:

    Please MS be consecuent, be smart, do not foolish to your customers, sample Windows Server 2012 R2 is out and Exchange 2013 SP1, is not, tak off you product architecture and put it on it again, put out TMG waht next to release a new version, due to poor
    implementation of Reverse Proxy for Exchange Server 2013 using IIS ARR and Support or your new idea Web Application Proxy with Windos 2012 R2 that needs to deploy ADFS, that sounds liek you previous trial of ADAM in DMZ, be serious in your directions, Lookup
    for an stable architecture direction in your other times I miss the times when Paul Bowden was Exchange Technical Product Manager, and sure that i am not the only one,

  93. Ridiculous says:

    No SP1 yet – end of Jan. This is absolutely ridiculous. I will suggest to mgmt, maybe it is time to look at alternatives.

  94. mike says:

    Yes we are at the end of January, what is Early 2014 to you? May? I have to upgrade a sbs 2003 with Exchange 2003 to Server 2012R2 with exchange 2013, and I can’t do that without this update. How long has R2 been out? which you’ve had more then ample time
    to work on the updates, at least put a mini update out with the r2 support into. You can’t tell me that you never had a release copy of R2 before it was announced. Talk about a company whose right hand dosen’t know what the left hand is doing. I may have to
    switch to a linux mail system if it taking this long

  95. Excnahge 2013 SP 1 says:


  96. MadAdmin says:

    While you guys aren’t busy releasing information SP1, can you please fix the TV app in Xbox One? It’s ridiculous that the app crashes with the error "For some reason TV took too long to start (0x8027025a)" all the time. Why don’t you throw Mark Russinovich
    at the problems and have him fix it? A) I’m sure he could and b) HE WOULD COMMUNICATE IN DEPTH ABOUT WHAT IS GOING ON.

  97. Early 2014? says:

    What does early 2014 mean> Real World = Jan 2014 MS World = 1st half 2014, perhaps it’ll be a early xmas present….

  98. Service Pack 1 Release says:

    Some Updates regarding the SP1 Release date ?

  99. Earl says:

    It is now February. When may we expect this release? When will it be applied to Office 365?

  100. Exch Admin says:

    Does early 2014 mean February, March or April? Can you guys give us a better idea? I believe there are many customers who want to deploy Exchange 2013 on Server 2012 R2.

  101. Luca @ KNE says:

    Are we in early 2014 or still waiting?

  102. Luca @ KNE says:

    Are we in early 2014 or still waiting?

  103. Avin says:

    MSFT we are already in feb 2014. Don’t you think we deserve a clear official release date now. This uncertainity is killing us, please…!

  104. waiting for godot says:

    "It’s done when it’s done!" you know ;) Seriously: I’m checking this blog for updates almost hourly for I have to deploy Exchange2013 on WS2012R2 too… Exchange Team: if it isn’t possible to anounce a specific date you could maybe name a period of time
    form now on to possible release date?

  105. M. Kaelin says:

    Can we get an exact date? I have to deploy several Exchange 2013 Servers… For one customer we had already put a 2012 Server in a 2012 R2 only environment… is very unfortunate.

  106. Mika Vistab says:

    Is your team working with the L&EDPS program to update their content?

  107. Michael E. says:

    Please give us a time line for the support of Exchange 2010 in an 2012 R2 AD Environment (not as a platform for the Exchange server). Different AD-Migration projects of our custommers have been stopped, because of Exchange Support missing. I think more
    than 3 month after the official relaese (and 4 month after the MSDN and Partner release) of Server 2012 R2 it is absurd to have no Support and no official timeline ….

  108. Colin Hunt says:

    As mentioned by everyone else in this post, we have many client projects waiting for this. At least, AT THE VERY LEAST, give us a date. Even if it’s further than you anticipated, just let us know. You’re making us look bad to our clients due to your misinformation.
    This is beyond ridiculous.

  109. Brian says:

    I am running a exchange 2007 upgrade project to Exchange 2013 on Windows 2012. Our servers are ready for install. My dilemma is install CU3 now and figure out how to upgrade to WIndows 2012 R2 later or install R2 now and wait for SP1. My Microsoft DSE
    feels waiting for SP1 is better cuz dealing with possible SP1 bugs outweighs having to try and upgrade to Windows 2012 R2 later when Exchange 2013 already installed. I guess this also leads me to ask can you inplace upgrade from windows 2012 to R2 when Exchnge
    2013 Sp1 is already installed? What you do all think?

  110. Joe says:

    I would like to know if SP1 will let OWA 2013 be able to view 2010 legacy public folders. I have an upcoming major migration to 2013 and can’t even consider starting until OWA 2013 can see legacy PFs. How can such an obvious feature be overlooked? I also
    see that you can add modern public folders to OWA 2013, but only mail folders–no calendars–no contacts. Will SP1 allow that too?

  111. Roger.H says:

    Seems people not letting up on this timeline thing :p. I’m waiting for 2012 R2 support as well but my test lab seemed to show it works as expected (in my deployment). I’ll still might hold off a bit though to get official support in the event I run into
    issues later.

  112. rdlabs says:

    Any news on the release date?

  113. Seth Technet says:

    I wish they’d release some type of update for us who are waiting so we can plan our upgrade projects…

  114. Baxter says:

    hurry hurry hurry hurry….

  115. Trev says:

    Tick……………… ;-)

  116. Josh says:


  117. Kevin says:

    Listen to your customers. Give us an update on when SP1 will be released.

  118. VdayPresent says:

    Because you love us Exchange Team, how about SP1 for Valentines Day? Please. You don’t even have to take us out to dinner.

  119. Zafar.Ali says:

    Guys, please leave Exchange team alone. I’m running on Server 2012 with Exchange 2013 CU3….I would rather wait and get a clean service pack that actually fixes some of the bugs and not look silly by installing SP1 and cause more problems than it actually

  120. That' only fair says:

    They are leaving us alone, so we should do the same.

  121. AlreadyLostACustomer says:

    They already lost me as a customer, I’m using google mail now

Comments are closed.

Skip to main content