Exchange Server: The Road Ahead

We’re approaching the one-year anniversary of the release of Exchange Server 2013. This is traditionally the time when people start asking questions like:

When is Service Pack 1 coming?
What’s the timeline for the next Exchange Server release?
What are you cooking up for the next version of Exchange?

This time around, we’re also hearing a few customers ask:

Will there be another version of Exchange Server?

We hope the answer to that question is obvious, but we wanted to go on record to make sure no one is confused. Here are the facts:

  • The Exchange engineering team is hard at work developing the next version of Exchange.
  • We expect the next on-premises version to be released according to our traditional release cadence (2-3 years after the previous version).
  • Microsoft has no plans to stop delivering on-premises releases of Exchange.

It’s true that customers are shifting their Exchange deployments from on-premises to the cloud, and it’s true that we are investing heavily in Office 365. We’re fans of Office 365 because we’ve seen that when customers run email in our cloud, they save money, they get larger mailboxes, and they get faster access to our latest innovations. IT admins spend less time maintaining servers and more time lighting up features that make users happy. Running Office 365 also brings us real-world experience that helps us build a better on-premises product.

While we are enthusiastic about the cloud, we also understand that our customers will transition to the cloud at their own pace. Many customers will remain on-premises or in hybrid deployments for the foreseeable future, and we want to keep delivering our newest and best features to them. Fortunately, our development process allows us to do that. We have a single code base that serves both cloud and on-premises customers, so we can deliver innovation to both groups.

Our development strategy continues to focus on Office 365 as the initial platform where we roll out new features. This approach allows us to introduce and test new features at scale before including relevant functionality into on-premises updates. The benefits of the strategy can be seen in Exchange 2013, where features such as Managed Availability are directly based on work done to automate and improve our datacenter operations. If you want clues about what’s coming in the next version of Exchange Server, keep an eye on what’s happening in Office 365.

It’s an exciting time for messaging and collaboration. Today’s technology trends— cloud, mobile devices, social computing, machine learning—all have the opportunity to make email more useful and powerful. We’ve got some great stuff cooking, and we’re committed to bringing innovation to all of our customers, whether they choose to deploy Exchange in the cloud or on-premises. The Exchange product team and our customers have a 17+ year history of successfully navigating changes in IT architecture and management together. We look forward to continuing that tradition with you.

Perry Clarke
Corporate Vice President
Microsoft Exchange

Comments (119)
  1. Anonymous says:

    From what I’m gathering of this post, the road ahead for Exchange appears to be disaster.

  2. Anonymous says:

    It seems the Exchange team has simply abandoned this blog and/or posts

  3. Anonymous says:

    Team must be on holidays, celebrating a year of not creating anything that works, and still turning a profit off licenses.

    Here’s an IT phrase for 2014: Post-Microsoft Solution

  4. Anonymous says:

    I, for one, will be recommending to my company (10K seat or so) to remain on Exchange 2010 based on current issues and the feedback provided here on this blog posting.

  5. David says:

    This is great news but you didn't answer one of the very questions that you brought up?

    When is Service Pack 1 coming?  

    For that matter, you initially promised quarterly releases for cumulative updates to correct many of the bugs present in Exchange 2013.  After the last snafu, you have not only passed that schedule but have gone dark as to when we can expect the next cu release.  Will you return to quarterly CU releases or will they be released as before (infrequently)?

    There are some very clear issues with on-premises Exchange 2013 such as the issue with transparent OWA rendering to existing E2K10 users.  This is an example of an issue that doesn't affect the cloud but on-premises users.  It is ok that MS is focusing on the cloud but this seems to be not in conjunction but to the exclusion of on-premises users.  The trickle down effect only seems to apply when the cloud and on-premises share the same issues or features.  In fact, when CU2 was released there weren't even any accompanying notes as to what was even being fixed.  

    So your post is well-intentioned and a good direction but doesn't even scratch the surface of the pain the on-premises users are facing when promoting your product.

  6. itworkedinthelab says:

    sounds good except one line:)

    "It’s true that customers are shifting their Exchange deployments from on-premises to the cloud"

    not exactly accurate when you consider all exchange base install compared to office 365(companies that migrated without everyone else… and DIDNT migrate back to on-premises)

    im an exchange fan, don't get me wrong, but from hearing what the majority of my customers say, they aren't going to cloud any time soon(from different reasons)

  7. Exchange 2057 says:

    It would be nice to see a more defined roadmap as David said – this will allow enterprise to plan their strategies as well….so Exchange 2016?

  8. The question I hear most is: what happened to the quality of the products and updates Microsoft (and specifically the Exchange team) releases. Well, the answer is that the focus shifted from on-premises products to cloud services. And I blame nobody expect for the upper management who decided that the company needs to become a Devices and Services company.

    And what good does this strategy bring us then? Managed availability is pretty much useless for on-premises deployments without SCOM because of the lack of user interface and reporting capabilities. What does it mean if 30% of the components report Unhealthy on a fresh out-of-the-box Exchange 2013 install? The other example I often hear is EAC which I'm told is what I should prefer over EMC because it's webbased. EAC is there because Microsoft needed it for Exchange Online, no on-premises customer asked to take away the previous interface with more features. Why do we see so many errors and warning in the event logs of our CU2 servers, why are there no real answers in the Forums except for 'me too, I see this too on all my Exchange 2013 servers'?

    So yes, I agree that the development strategy continues focusses on Office 365. But please be honest and don't tell us that this brings only benefits. Let me wrap up my rant with another question: Many customers are looking for guidance to configure Server 2012 R2 WAP for the publishing of Exchange. Can we expect a whitepaper similar to the excellent TMG and UAG ones?

  9. Mindaugas says:

    Need more clear road map for CUs. It was stated one every quarter, but it seems it already slipped the date. There are issues in CU1, CU2 and no interim fixes are offered. I have few large customers waiting CU3 to fix some of the production issues.

    when is CU3 coming? or SP1? I noticed cloud servers had been updates some time ago…

  10. Richard says:

    We are also very interested in SP1 as well. Any guidance on this would be very valuable for us.

  11. Bernd says:

    When will Exchange 2013 be supported on Windows Server 2012 R2?????

  12. Nino Bilic says:

    Folks, sorry to tease on SP1, look for a follow up post on SP1 timing very soon.

  13. Lis says:

    I think PRISM will bring them back to OnPremises.

  14. Arnor says:

    Bring back a decent spam filter for Exchange 2013 on-premise. The out of box one is no good. I have no interest in the cloud hosted version.

  15. Madu says:

    Exchange 2013 product and especially CU update quality is really, really poor. Many admins are afraid to install CU updates fresh when they arrive since there are many cases where it might corrupt entire Exchange installation and lead to severe outage and disaster recovery scenarios. The situation now is that one needs to wait 2-3 months before applying CU's to see if someone has broken their environment and blogged about fixes and tips to prevent that from happening. Currently waiting for CU3 to a known issue with Health Manager after spending hours and hours with Premier support. Can't really recommend upgrading to Exchange 2013 to any customer at the moment.

  16. Rajeev Ujjwal says:

    Well, there should not be any issue if customers are either moving or remain on-premises Exchange 2013 from previous Ver. of Exchange. The Product still from MS and if Customer are happy on-premises/private Cloud then let them to be enjoy/satisfy on it. Looking on SP1 so that product can be more stable.

  17. bill says:

    NSA PRISM revelations has put a stop on Public Cloud / Office 365.

    So Microsoft wake up :-) and give us a super Exchange 2013 SP1 On-Premises.

  18. Simon says:

    Please, PLEASE, **PLEASE** give me proper on-premise anti-spam filtering in Exchange 2013. Currently I have to run Exchange 2010 just for this functionality… !

  19. Joe says:

    "It’s true that customers are shifting their Exchange deployments from on-premises to the cloud"

    That is NOT true for your Worldwide customers, after the NSA PRISM revelations.

    Wake up Microsoft…….

  20. Vientos says:

    When will be a SP, because with Exchange RTM, CU1 and CU2 V1/V2, are not ready for coexistence, I have the following issues:

    1. The adminsitrator user has not all the rights to administrate the organization. Even when we include the user in the Enterprise admin group

    2. The mails sended from Exch2k13 to Exch2k10 stuck in drafts, when we try the reverse (ex2k10 to ex2k13) is stuck in the queue

    3. in our current environment (ex2k10 SP3 and an edge server ex2k10 SP3) Exch2k13 takes the mail flow control and all mails stucked in the transport.

    4. The queue viewer not work!!!!, we use the queue viewer of ex21k0 and we cannot view the queues of ex2k13

    5. Cannot connect to the EMS with administratives accounts because we receive an error message regardin WinRm, despite the WinRm are correctly configured

    In short Exchange 2013 is a mess, released to the market without the tests of coexistence completed and another tests of full functionality done it.

  21. Chris_Merritt says:

    Speaking from experience, I have just one thing to say, please please please don't de-emphasize on premise support over Office 365. We run a large number of Exchange servers using the on-premise version, and all we want is to see you guys support the on-premise releases just as well as you do the Office 365 ones.

    This to me means releasing the same features for both, and making the tools and functionality work just as well for your on-premise customers as it does for Office 365, and keeping licensing costs competitive (which have been increasing as your own per mailbox costs go down, this is pretty anti-competitive!).

    It feels like to me like the focus is on getting everyone onto Office 365 with little thought put to those that can't or don't want to go to Office 365 for various reasons.

  22. Cu3 says:

    Cu3 when????????????????????????? Why ms said 3 months if they can't achieve it.

  23. Theprivatefolder says:


    maybe without connection to this specific topic but:)

    how can companies go backup less(and at the rate were going a lot will) when single item restore doesn't restore folder trees?(on mailboxes and public folders which are now mailbox public folders)

    this is one heck of requested feature that's blocking many customers from going there because of the size of mailboxes or public folder(or public folder mailboxes)

    Any idea?

  24. raman03 says:

    The very first step of co-existence of Exchange 2013 with 2010 is re-direction for OWA.  I installed 2013 in test with 2010 and the first thing which should be working out of the box is OWA re-direction.  I am stuck like many others with basic re-direction issues.  It has been days since I have been struggling to get it fixed and no progress in further testing.  No answers on forums, large number of people seeing same issue.  

    I never understood why Microsoft clients (Exchange administrators) need to put so much time in making things work which should be working with minimum time and efforts.  Instead of working on Exchange architecture and design we all are working on to make re-direction work.

    May be after sometime we give up and start opening up support cases with Microsoft and start paying them for support for no real reason or problem.  

  25. Vientos says:

    Dear community, this means MS (and the partners who support the installed base of Exchange) is pushing to the clients to buy Notes or another mail system to replace the Ex2k13, in latin america many of our links are not to good to move the infrastructure to the cloud. I'm asking myself, is Microsoft consider this? or only consider the customers in another regions where the access link to internet are far reliable than the latin american links.

    In my particular case, I supported Exchange since the 4.0 version, and now i must'nt recomend the migration, because the mail infrastructure cannot coexistence in a transparent way.

    Throw away the good job for only one third of clients is a very bad policy.

  26. Bharat Suneja [MSFT] says:

    @Vientos: This post reiterates that Microsoft will continue to ship new versions of Exchange Server as it has been in the past, every 2-3 years.

  27. ML49448 says:

    A nice update for the focus on O365; however the on-premises deployments continue to suffer and even worse for Microsoft… move to be virtualized on VMware. That begs the question, has the Exchange team changed its stance on virtualizing? The constant message has been that virtualization adds too much overhead to an Exchange deployment; however the statements above seem to indicate a softening of that stance as Exchange's direction heads to O365. (my guess is that the O365 infrastructure isn't all physical boxes and DAGs) This is especially intriguing considering Perry's comments regarding the Exchange team being "committed" to bringing innovation regardless if a customer chooses an on-premises or private cloud.

    This directional shift would be very interesting for Microsoft to confirm as there has been a very steady message for some time.

  28. Barebodkin says:

    Some clarification regarding current and planned support for Server 2012 R2 needs to be available. We shouldn't have to poke around non-Microsoft Internet sources to find out what problems might arise if, for example, we update domain controllers. This info should come directly from you guys and promptly.

  29. Stephen Frost says:

    What I would like to know is when Microsoft are going to address long-standing bugs like this one:…/sync-error-every-time-i-send-an-email

    Not interested in Cloud.  Not interested in Exchange 2013 or later.  Not even interested in Exchange 2010.  Not interested in Office 365.  Not interested in Office 2013.  Not even interested in Office 2010.

    Still running Exchange 2007 and Office 2007 and will be until I see some evidence that Microsoft are fixing bugs that have been reported Over and Over and Over again.  Wake up guys.  Speak to your management.  Customers like me are NOT happy with stuff like this … and I am telling my management "We are NOT buying any more Microsoft products until I see evidence that they are fixing such widely-reported bugs".

  30. Glibglob says:

    I work in healthcare and for legal reasons, we cannot simply shift to the cloud. A good proportion of organisations out there also will not move to the cloud for valid reasons. Since the focus on O365, I have seen a marked shift in Microsoft's level of support for on-premises environments e.g. no real Exchange 2013 BPA, most troubleshooting tools are gone, EAC is extremely limited for no good reason e.g. using the shell should not be mandatory for one-off tasks because its easier to do things like that from a user-friendly GUI; it should only be necessary for making mass changes or automating tasks. If your focus is going to be on the shell to the neglect of the GUI, then we might as well all move to UNIX-based applications. I think this is lazy programming — putting a user-friendly GUI on top of things was what made Microsoft products so popular in the first place. Unless there are significant improvements to the next version of Exchange, then I won't be recommending it to management.

  31. Tibor M says:

    Hi, that's blog is really nice but totally useless. We are waiting for CU3 and it still not coming. Are you serious that users can't forward external event invite to other people? How is possible that this is not working? Isn't exchange groupware? Isn't it's basic functionality receive and send emails? Guys, do harder, because it looks like you're doing nothing.

  32. Albert Widjaja says:

    Yes please, I'm hard pressed to recommend the Upgrade to Exchange 2013 to my management, because there is no real value to the business, so I guess I'm still on 2007 until it is out of support.

    Please let us know when is the SP1 release date ? so that I can expect some good news to remedy the issue described by most people in this forum and especially this blog:…/exchange-server-2013-gotchas.aspx

    I was on my way to pursue for MCM (Certified Master in Exchange Server, but somehow Microsoft has disappointed me and lots of people out there as well.

  33. Ronpr says:

    Looks like he was in a hurry for eat or something that didnt answer his own questions.

    When is Service Pack 1 coming?

  34. Rhys says:

    Just did an Exchange 2010 to Exchange 2013 Migration today.

    It failed completely, and we'll stay on Exchange 2010 for probably a few more years. Outlook Anywhere (RPC Proxy) appears to be totally dead. Few hours of troubleshooting could not fix it. If theres a TechNet article, we've read it.

    The road ahead: Exchange 2010. As mentioned by a lot of other people in this thread, 2013 has serious issues, and Office 365 support/reliability in Australia is a joke.

  35. ML49448 says:

    When will Exchange 2013 be supported on Windows Server 2012 R2?

    >> We are waiting, because we have to migrate our Exchange 2007 environment to Exchange 2013 and we need to use Windows Server 2012 R2.

  36. Sven J says:

    When Exchange 2010 will support IE11 ?

  37. pac says:

    Exchange 2010 worked perfectly out of the box. E2013 is almost a year old, but still a beta product which is full of bugs even with CU2. If MS start to sell something that should be as stable as E2010 was on day one. This article has one message to me. Microsoft's priotrity is not the on-premise exchange nowadays.

  38. TJ says:

    The greatest business decision of ALL time.

    1. Invest in a software of 20 years (Exchange).

    2. Get 80% of corporate Email market worldwide (Exchange).

    3. Get 400 millions corporate mailboxes worldwide (Exchange).

    Then Microsoft Management decide forget about Exchange On-Premise everyone should go Public Cloud.

    Price less for Microsoft…………….LOL……….

  39. ABCFED says:

    "The question I hear most is: what happened to the quality of the products and updates Microsoft (and specifically the Exchange team) releases."

    That's the same question I keep hearing and wondering myself as well. Quality has really nose-dived with the onsite Exchange 2013 services. IMO, Exchange 2010 is in a lot of ways still the superior product even today.

  40. lee says:

    Microsoft listen to TJ here.

    You have a successful Exchange On-Premises software so continue investing on it.

    Do not DESTROY the software you have created 20 years ago & worked so hard to become a Messaging leader software in the world.

    What stuff Microsoft management smoking :-) ?

  41. ThommyG says:

    "We’re approaching the one-year anniversary of the release of Exchange Server 2013." No reason to be proud guys. One year is gone and Exchange 2013 still is beta software. I even cannot recommend this software to our customers without risking to loose them. Your former flagship is sinking. Fast. And Office 365 is not an option. Exchange 2010 of course is.

  42. btucker says:

    "We’re approaching the one-year anniversary of the release of Exchange Server 2013."

    and it is almost like you did nothing for the entire year. users still dislike the new OWA interface regardless if it looks terrible on more supported platforms now. MAPI, Edge, and other services have been removed and  features degraded. We don't even have a decent GUI interface anymore. Bugs still plague the product. We can't even install the base product into an existing Organization without it immediately breaking the client CAS connectivity and we have to drop to PS just to set the uri to null. Exchange appears to have regressed tremendously with this version. Now, even the CUs are not being released on time anymore and countless patches have been recalled.

    yes, it's the one year anniversary and on premises Exchange is still in terrible awful shape. Agree with a previous poster that this is nothing to be proud of. I might add that I've never seen such shoddy work from the Exchange team before. This is not an anniversary to be proud of.

  43. gerard says:

    You have a lot of nerve posting a blog like this and/or are showing how out of touch the Exchange team is with its customers and reality.

    "The Exchange engineering team is hard at work developing the NEXT version of Exchange" with focus on Office 365.

    However, the engineering team should be hard at work finishing the CURRENT version of Exchange to make it stable and useable for on-premises customers.

    One year after it's release on-premises users are still not able to do something basic as forwarding a meeting request to another user, we get complaints about this almost daily.

    "Running Office 365 also brings us real-world experience that helps us build a better on-premises product. " and "Our development strategy continues to focus on Office 365 as the initial platform where we roll out new features. This approach allows us to introduce and test new features at scale before including relevant functionality into on-premises updates. The benefits of the strategy can be seen in Exchange 2013 …"

    On-premises customers have not been able to see these benefits or a better on-premises product at all. Despite it's issues with rollups, Exchange 2010 was a much better on-premises product, and while you are regularly deploying new Exchange 2013 builds on Office 365, we are still stuck with an unstable CU2 build with lots of unfixed issues and we have received untested broken updates.

    You guys are still pretending that Exchange 2013 was a succesful release for on-premises customers and something to be proud of, when in fact it has been a complete and shameful failure so far, having caused lots of reputation damage. The whole NSA PRISM situation won't exactly help adoption of the Online version either for many customers.

    Your blog is not giving us much confidence that this situation will improve going forward.

  44. art says:


    Or loose 20 years of investment in this software. As the old saying goes "It takes a lifetime to build a good reputation, but you can lose it in a minute."

  45. PleaseListenToYourCustomers! says:

    I think Microsoft's Exchange team is starting fall into the nasty rock star habit of believing their own press…

    Hopefully the constant and repeated overall message pouring in from the comments here show them that they fell down on the job supporting their on-premises customers in pursuit of a cloud solution. Then again I think it’s wishful thinking they will acknowledge the problem and change course for the better.

  46. says:

    While I can appreciate this post and the message within (even if not all questions raised in it are answered and it's still IMHO very focused on O365), I do have some suggestions i hope you take into consideration going forward.

    Like multiple commentators mention, there are bugs in Exchange 2013. With a complex product, that's not weird. I am however disappointed because there is less information publicly available compared to older Exchange versions (it is a subjective feeling). I also haven't seen a complete list with fixes with CU1 and CU2. I don't need a solution or a workaround. Just an acknowledgement could help IT Pros with explaining the situation to non-technical key persons (and prevent being wrongly blamed for incompetence…). More concrete information on new CU or SP release dates could help accepting a current sub-optimal situation.

    It proves in my view that Microsoft is still invested in on-premises deployments and not chasing customers in the cloud because on-premises deployments have become too difficult.

    But it is also possible that customers see/hear/read about issues with Exchange 2013 (whether they are correct or not) and hesitate to move to Office 365 as it is relatively well known on-premises shares the same code base as the cloud version.

    Basically, on-premises Exchange is still very important for Microsoft and certainly for those IT-Pro's that design, implement and administer them. I do believe that with a bit more effort you could help IT-Pro's a lot.

    These where my 2 cents and I hope you appreciate my attempt to reply with constructive comments/criticisms and that you find them helpful.

  47. Hi Perry,

    Unlike many of the Exchange team post this one is surely one of the worst posts. I don't understand the point of it at all? Was it innovation, vapourware, O365 or first post for me? Please explain to the many recent replies here what you wanted to get across – certainly you did not answer:

    When is Service Pack 1 coming?

    What are you cooking up for the next version of Exchange?

    I am in agreement that your team is presenting a view to the outside of 'marvellous job this year' when actually you are 1 year from original product release that had less functionality in many ways to its previous release and updates and literature severely lacking. I think your post should have been 'Exchange Server – on premise and what we should have provided by now'

    Finally – the reason I like the Exchange blogs is because they are normally detailed, well presented and become a core part of most peoples knowledgebase. I hope this blog does not descend into something akin to a twitter feed.



  48. Mindaugas says:

    48 hours passed after this blog was posted and there is no response form the author to address any of the concerns..

    It looks like Exchange team is agreeing with all what we say, and do not have much to add… Sad…

  49. k. J. Hall says:

    i am more confused on the road ahead for Exchange than I was prior to reading this blog.

    First, is anyone listening to these issues? if so, when can we expect a list of answers to the countless valid questions being raised?

    Second, when is sp one coming out? Two days after posting this, you have still failed to answer your own question. same with feature details for the next version. what are they?

    Third, you mention working pn a future version of Exchange, but wait a minute. You haven't finished the version you just released and are now delaying critical patches. How about no. How about stopping ALL work on future versions and fixing the version you have out there right now?

    so, color me completely confused and unhappy with the direction things are going here.

  50. JoetheITguy says:

    We got two words for Public Cloud / Office 365 = NSA PRISM

    Sorry guys now that the cat is out of the bag PLEASE continue investing on the Exchange On-Premises

  51. ABCFED says:

    3 days after posting this strange blog…there is still…confusion in the air. Massive valid questions and/or concerns are not being answered.

    Worst blog post…ever.

  52. Tibor M says:

    I have opened business critical case on friday with very little possible chance to success resolve problems with forwarding external invitations to internal collegues. So try to guess what MS said?? :D

    Classic MS answer on technical support: "This is known bug, we still do not have any workaround, but our developers work hard to deliver patch as soon as possible. It will be release very soon. We let you know."

    So what is result? migrate to Google Apps boys? It's *** by my opinion, but do we have any other chance? Exchange 2013 is really *** product now.

  53. arif says:

    Confusing. No clarity on this post.

  54. ExchangeUser says:

    The Exchange team really missed the boat by not enabling on-premise to run all exchange servers are core-only.

    After all, if it's all managed via an internal URL, what's the point in having anything running on the Servers themselves???

  55. a Customer says:

    Microsoft you have FIFTY comments now telling you, give us a SOLID Exchange 2013 On-Premises.

    And invest on your Exchange On-Premises software.

    We hope you will lesson or you will lose your worldwide customers.

  56. markus says:

    No company with a minimum interest in data security will ever give out their data to a diffuse cloud service – not just since NSA etc. I know dozens of mid-size companies that use Exchange and not a single one of them has any plans to move their servers or data to the cloud.

    On the other hand, I can stress the complaints of other comments: Buggy initial versions, compatibility problems, reduced testing, especially of localized versions. Instead, we get 'rapid releases' that simply cost enormous admin time to install and debug. Interfaces that might look ok on tablets, but are horrible on desktops. Get real: who manages Exchange with a tablet?

    Learn to listen to what your customers really want.

    Not interested in Office 365, Azure, Ex2013, Win 8.1.

  57. Matthias Fleschütz says:

    I really support what Jetze Mellema wrote already…

    Although from technical aspects the product is improving more and more the all-over-quality is suffering really. We were just deploying Exchange 2013 CU2 freshly into our environment and as we are a software company too,

    I just can say: we would be bancrupt if our product would have such a quality!

    It is not possible to get Exchange2013 running cleanly in a fresh environment…..? Seems so…

    The product strategy from MMC to web…quite well, but it is more unpredictable how the system behaves by using the same named function via web or via client…

    And more like these issues, everybody of us knows already…

    Therefor I cant understand this focussing on O365…and Managed Availability. Do you really think that every company will have its e-mail infrastructure outsourced? Or is it just for giving the NSA easier access…;-)

    Have Exchange after years (I started observing it with Exchange5) at a point where it is technical usable to would be great to have it a) stabilized and b) finally fully and seamless and consistently (!) integrated.

  58. Lynn says:

    I have been a fan of Exchange for many years. However, over the years, since Exchange 2003, the EMC, ECP, EAC functionality has been reduced to a point that it almost gives us no decent functionality whatsoever.

    Gui's exist for a reason, and while Powershell is a good tool, it's NOT the end all be all for management of Exchange Server.

    I tried to perform a very simple task today, filter email boxes and groups that contained a specific keyword so I can check all their settings. All other versions of Exchange had this spiffy little feature that allowed you to filter your results, but low and behold, Exchange 2013 replaced this with a search feature that is pretty much worthless.

    I'm doing my best guys, but I'm about to write off Exchange after 10 years of being an evangelist for it. Please fix the issues, namely stop removing functionality from the EAC that actually helps people do their jobs. As said before, Powershell is great, but it isn't suited for all management tasks. I don't know what focus groups you are listening to, but we need functionality, not powershell.

  59. Jack says:

    no answer for SP1, from Exchange 2013 I cannnot see the future of Exchange on-premises.

    Will customer make U-turn to office365 or Microsoft U-turn to on-premises? Who knows??

  60. Glad to see I am not alone. Long time Exchange admin. Loved the product until 2010.

    85% of the mailboxes I look after are not going to the cloud in the "foreseeable future".  15% are already there, and will stay there.

    Exchange 2013 OWA / ECP / Spam are my main issues. Update quality also.

    In general : Web interfaces are inevitably inferior to multi-gigabit LAN interfaces.

    For the Exchange team and Microsoft senior management – you can get us to pay for software assurance, but your cloud offering is as far from convincing as Exchange 4.0 was when I first used it. Keep us onboard and remember that there is a world outside the USA. (most of it)

    Server 2012 R2 is a GREAT product. Support it. System Center 2012 R2 is crappy but improving. Why is Exchange sliding downhill?

    Probably because the senior management have decide to push the flagships over the brink first in the hope that the customers will follow. We won't unless we are convinced. Windows 8.1 team watch my lips.

  61. It's too bad says:

    Seriously, I have been a long time fan of Exchange and a promoter.  But I have used 2003, 2007, and 2010.  I see no reason at this point in time to invest any time or money into 2013.  I just see a headache and waste of money, no ROI, an on-premise logistical nightmare (have to remain on premise for legal reasons), no GUI (again, is this regression?), and just a lack of support in general.  This post says a lot.  There aren't too many reply from any MS moderators or reps.  It's time to do some serious thinking on the MS side as the entire  E2K13 thing seems to be a failed project.  And I mean no disrespect.

  62. Exchange_ Fan says:

    I am always a fan of Exchange server, it's a great product specially Exchange 2010. But recently how Microsoft started treating Exchange, really disappoints me. Exchange 2013 is another Vista! Microsoft, please stop doing experiments with your flagship products! Your recent approach towards on premises Exchange has already shaken the morale of your loyal customer base. Please listen to your customers and give them what they want and not what you think they should get. Look at the whole messaging eco system, you radical changes, no clear product road map in place is making other 3rd party product developers crazy and the end user is always at the receiving end.

    As far as the Office 365 is concerned, it's a total mess. One service outage after another. Once of my clients recently lost a larger volume of mails due to one of such recent outages and most funny thing, if you call the support, you will get a response, "We can't recover those mail." Come on, Microsoft! Are you using your Office 365 platform for bug tests with customer’s data at stake? Most of the time, they deploy some patches the back end without any prior intimation and when it breaks something, it takes another couple of days to fix it and in the meantime, you are left with only praying and hope someday it will be fixed.

    Microsoft, you can't sails two boats together, decide, either you going to remain as a product company and deliver some of the finest products like past days or be a support company and drive everyone crazy with solutions like Office 365. I am a diehard fan of Exchange and can't see this product tearing apart due to mismanagement.  

  63. Frank says:

    Why aren't you answering all of your own questions you ask yourself in this blogpost? People are waiting for answers. Unbelievable that you even don't answer questions asked in the comments.

  64. Hello all,

    My second post – Still nothing eh?

    Microsoft Exchange Team – please can you look at this post and expand on the original post and reply to the many, many comments? The additional post on Outlook configuration shows you are active and I cannot believe you are ignorant to all of these comments.

    My belief is the quicker the better as comments are moving from constructive and generally confused on the original content, to being more angry and irritated at the silence and product roadmap / strategy.



  65. Mindaugas says:

    Agree with Terry. At least acknowledge that you agree with comments and provide some answers.

    ps. So far it is completely useless blog post, only made us all angry..

  66. Petri says:

    Microsoft decided to integrate Exchange to Active Directory a long ago which I think was a bad decision from cloud era point of view. Everything works fine in one AD Forest but when you need something else it can became a really nightmare. Basically Microsoft is trying force to change the system (which was originally designed only for on-premises environment) to work in the cloud with variable success. We all know how tight Exchange is integrated with AD (especially Configuration partition). In the past it may seemed a good idea to store all the configuration information in AD but it has become a burden. This O365 mess is just too complicated to handle for Microsoft itself. Google and the other cloud providers didn't had that background and they could start from the scratch. To separate Exchange from AD could be one solution but backward compatibility might be loosed but that could be a wise decision in the long run. It would be a really nice to run several Exchange instances in your on-promises network and in one AD! Now you have only one Exchange organisation in AD/Forest and every time you want to install new versions from Exchange you have to upgrade that one Org and keep fingers crossed that nothing breaks. It looks like version 15 is some kind of "Exchange Vista" something that we can forget as soon as possible. Looking forward to see where the Exchange will be going… I still have high hopes.

  67. Marco Novelli says:

    I'm a Windows / Exchange Sysadmin since Windows 2000 – Exchange 2000

    In one year of Exchange 2013 I've deployed just one installation in a green field and was quite a mess

    I have no plan to migrate to Exchange 2013 any Exchange 2007 – 2010 customers until SP1 and Windows 2012 R2 support

    In the meanwhile I've migrated all little customers (under 50 mailbox) to Office365 and I'm pretty happy with that cloud service

  68. Patel says:

    Why these Public Cloud companies (Office 365) do NOT get it.

    Companies will NOT hand over their beard & butter (Emails) to the Public Cloud, especially after the NSA PRISM.

  69. Patel says:

    In the above comment I meant "Bread & Butter" I.E. Companies will NOT hand over their livelihood (Emails) to the Public Cloud (Office 365).

  70. ThommyG says:

    Why not He should shed some light to this Exchange disaster.

  71. Hi everyone – your feedback about the disappointing quality of on-premises releases has been heard loud and clear.  We’ve made changes to our processes and systems over the past few months in order to course correct.  We’re committed to deliver better results going forward.  

  72. Brian Shiers [MSFT] says:

    @Michael You have options and we provide virtualization support for Exchange 2013 and understand this will make sense for customers – refer to…/jj619301(v=exchg.150).aspx
    and regarding our preference you should review the Virtualization session from TechEd –…/OUC-B326

  73. @David and @Dave Stork – You are absolutely right about us not providing enough documentation regarding the fixes in CU1 and CU2. We took this feedback to heart, and with CU3 and later releases we will include a Knowledge Base article that outlines all customer reported issues that were resolved in the release. In addition, the Release Notes on TechNet are updated at each release to discuss known issues and any new features or enhancements that are introduced.

  74. Kevin says:


    "Hi everyone – your feedback about the disappointing quality of on-premises releases has been heard loud and clear.  We’ve made changes to our processes and systems over the past few months in order to course correct.  We’re committed to deliver better results going forward."

    You haven't even answered the questions this post itself raises. For example, when is SP one coming out? What are the next features fro the next version? People are wondering where the quarterly cumulative update releases are and you are silent. Issue after issue has been raised here and you, again, are silent.

    What exactly are you committed to?

  75. @Mindaugas, @Cu3, and @Madu – CU3 is going through its final testing and validation and we aim to have it out to you in the near future.

  76. Kevin (again) says:


    You previously committed to having CU's released every quarter. Now, it has been over a quarter you still don't even know when the next one is going to be released?

    I'm sorry, but this is smacking of incompetence.

  77. Vientos says:

    The questions are still in the air:

    Is Exchange Server 2013 CU3 (or with SP1) capable to offer a transparent migration and coexistence with legacy (2007/2010) servers, and with full capabilities of monitoring and smooth steps to support the scenarios with multiples legacy servers

  78. @Kevin – The goal of Perry's post was to confirm that we'll be shipping future on-premises Exchange Server versions.  We'll address related questions like the timing of SP1 and the timing of CU3 in separate blog posts that will arrive in the near future.

  79. Kevin (yet again) says:


    You are being overly vague, like you are making this stuff up as you are going along. You seriously have no planned release date for CU3 at this point?

  80. engedib says:

    Kevin (yet again),

    CU3 should be released in the next few days, some of the KB articles have already been indexed.

    Search for this:…/2892464


  81. Marcel says:

    Before developing a new version please stabelize the current version 2013, bring back all the features in the ECP which was available in the version 2010. The developing cycle of new versions should be not every 2-3 years, better it tooks longer but we receive a stable full functional product.

    I think the most customers which use exchange not want move in the cloud, even if microsoft try to force them. It's good to have your data in your hands do know what you do with it.

    Hope microsoft understand this and focus back general on relaible business solutions.

  82. Listen says:

    MS you need to Listen now & send this Blog to your MS management.

    1. Most of your customers do NOT want to move to Public Cloud (Office 365), for many reasons (NSA PRISM, data security, data control, Private Cloud………..).

    2. You MUST improve your Exchange On-Premises software Quality Assurance, do NOT send us buggy software.

    3. This blog can be a bridge between you & your worldwide customers, LISTEN to them.

    4. It took you 20 YEARS to get a flagship software (Exchange On-Premises), do NOT destroy it now. You have 80% of messaging worldwide market share with Exchange On-Premises, be smart.

  83. Kevin says:


    "CU3 should be released in the next few days, some of the KB articles have already been indexed"

    Is that the official Microsoft statement on the matter? So, we can expect CU3 by the end of this week? Why was it delayed?

    When can we expect CU updates in the future, since it is obviously not going to be quarterly anymore. When can we expect SP1, which was the very first thing mentioned in this article.

    This is crap.

  84. @Tibor M & Gerard, I agree the issue preventing external meeting invites from being forwarded in CU2 was entirely unfortunate. Thankfully it is one of the many items resolved in the CU3 build you will be receiving once it completes the final validation tests Jon mentioned earlier.

  85. ABCFED says:

    It certainly was a LOT more than just meeting invites being forwarded that has issues with CU2. You realize there are certificate issues, migration timeout issues, routing issues, and others.

    Last time I set up an Exchange 2013 system with CU2 I had to call PSS twice. Both times it was determined a bug and they did not charge the incident. The migration took well over 24 hours longer than it should have, again due to bugs. That customer (200 users), has asked me how they can migrate BACK to Exchange 2010. They absolutely hate managing Exchange 2013 from the admin side and the users hate the new OWA look. I'm not kidding about that…I have a customer right now who wants to rip Exchange 2013 out of their environment and are even considering standing up a resource forest just to get of 2013 and linking mailboxes. It's THAT bad.

    Also, Is nobody ever going to answer the question this blog raised?…which is…when is SP1 coming out?

    It's been a week. I see a few Microsoft Exchange team members scrambling to try to save this blog post, but you ref forts are nowhere near good enough. Also, what are the new features of Exchange on-premise you are developing for? This is YOUR blog post and YOU raised those questions, yet you fail to answer them…even after a week?

    What is going on with the Exchange team? Something is obviously not right. Is it resources? Are there not enough Exchange engineers to do the job right? Is everything just so top management heavy that simple tasks like releasing patches on time that work…just can't be possibly done anymore?

  86. Geoff-P says:

    I've been using/administering Exchange since Exchange 5.5 and just wanted to jump on top of the pile to voice my concerns as an enterprise customer.

    1. The lack of support for Server 2012 R2 is disappointing. With the accelerated release cadences of Windows and Windows Server, Exchange should really run on the new version of the OS in a timely manner. Lync 2013 already has update out to support Server 2012 R2, and Lync is a fairly complicated product in my opinion.

    2. The disappearance of the Edge role. As a customer, I liked having the choice to run anti-spam in my DMZ instead of going to Forefront/Exchange online. It seems as if the only way to do that now is to keep an Exchange 2010 Edge around or buy a 3rd party product? So I like using the Microsoft software but you guys are actually pushing me toward using a 3rd party for anti-spam.

    3. Not 100% Exchange, but killing off Forefront for Exchange also sucks. You go from having an A/V solution which I could run on the Hub/Mailbox servers in 2010 that had multiple vendor A/V engines to the malware protection in Exchange 2013 which has one engine, not as many options and doesn't get as frequent definition files. Really?

    4. The cloud / Office 365 should be marketed as Exchange for dummies. While I respect the cost advantages to the cloud, as someone who likes setting and maintaining Exchange on-prem and as a company, we're not ready to move to the cloud yet for email, so please continue to invest in, develop, and release on-prem features in a timely manner.

    5. We, customers, all know that Exchange is really the only choice for enterprise email. I mean the google crap is just crap. So please bring back the quality we saw in the Exchange 2007 – 2010 era in Exchange 2013 and beyond. Don't leave behind the on-prem customers who have helped grow your product.

  87. Bharat Suneja [MSFT] says:

    @Geoff-P: Thank you for the feedback. Note:

    1. Windows Server 2012 R2 was
    released less than 3 months ago
    . Exchange support for newer Windows Server versions usually follows in the next service pack.

    2. The Edge Transport server role has not disappeared. When we released Exchange 2013, we indicated this role won’t be available at RTM. It is included in Exchange 2013 SP1. See today’s post:

    Exchange Server 2013 Service Pack 1 Coming in Early 2014

    3. Thanks for the feedback on ForeFront Protection for Exchange.

    4. Re >>The cloud / Office 365 should be marketed as Exchange for dummies.

    We recognize that most customers will not transition to the cloud overnight, some won’t in the foreseeable future, and some customers may never do so for various reasons. However, as far as admin capabilities go, the fact is that Exchange Online and Office
    365 provide IT Pros a great administration experience. If you’re familiar with on-premises server products, you use the same familiar interfaces –
    EAC and
    – to manage it (along with the needed "glue" to sync directories that you would use in multi-forest environments even in on-premises deployments, and ADFS for Single Sign-On).

    5. Thanks again for your feedback! As this post indicates, we are committed to and working hard on the next release of Exchange Server.

  88. ThommyG says:

    …and please IMPROVE the setup routine! My last setup failed because of a trailing space in the enviroment variable "PSModulePath", wherever this came from, but this is a known issue. It was a fresh installed Windows Server 2012. After fixing this I had to restart the setup twice to be able to continue the setup process. With 98% completion the setup windows just disappeared without a "Setup finished" message or something similar. It just disappeared. I had to inspect the Exchange setup logs to find out that the setup was completed. Another issue: after re-issueing a certificate from our CA with all required names and binding all the services to this certificate everything seemed to work well until i restarted the server. Nothing worked after that restart, e.g. EAC, Powershell, Outlook, Redirection. I found out, that after the restart the Certificate binding for SSL in IIS was gone. Ok, this was also easy to fix, but do You really think that issues like this give trust in Exchange 2013? OK, right now i have a working Exchange 2013 co-existence with Exchange 2010, our reverse proxy forwards requests to Exchange 2013 and the hidden redirect works well for OWA, OA, and EAS. But I won't go any further like moving mailboxes from Exchange 2010 to Exchange 2013 or building a DAG before SP1 is available. And please also rethink the Public Folder migration process. This is not acceptable for customers with big PF installations, which exist in real world environments. I completely agree with all the posters. The poor quality of Exchange 2013 , the Windows 8 and Server 2012 GUI (i still cannot belive that someone decided to put this GUI on such a good server platform), the discontinuation of TMG and Forefront for Exchange are just some examples of wrong and irrational decisions which leave a lot of people speechless.

    Btw: Why the Lync team is able to do so much better? Their product Lync 2013 is awesome.

  89. Concerned says:

    >>> When is Service Pack 1 coming?

    Over a week and nada

    >>> What’s the timeline for the next Exchange Server release?

    We are still left wondering

    >>> What are you cooking up for the next version

    Not a single idea has been shown.


  90. Zoltan Erszenyi says:

    @Bharat Suneja, "5. Thanks again for your feedback! As this post indicates, we are committed to and working hard on the next release of Exchange Server."

    To me that sounds like MS has plugged tight its ears and doesn't hear the outcry of its worldwide admin base regarding the issues in Ex2013. Hence we cannot expect real focus on fixing the pain. Instead, what we get is yet another rushed product to meet your crazy timeline to release new software which probably will not bring anything new that would be of real use to anyone.

    Here is another question for you, MS: what business need prompted you to create a new version of Exchange – I mean not YOU need to keep up with the new release pace at any cost, but REAL needs of your user base in the greater world (a.k.a. beyond the gates of Microsoft's headquarters)? What business or technical need isn't met by existing versions of Exchange? Do we REALLY need yet another new bag of bugs in 2-3 year's time?

  91. Bharat Suneja [MSFT] says:

    @Zoltan Erszenyi: The "next release" include the upcoming CUs & service pack for Exchange 2013, in addition to the next version of Exchange.

    For SP1, please check the release announcement posted on the blog today –
    Exchange Server 2013 Service Pack 1 Coming in Early 2014

    We continue to gather customer feedback on issues with Exchange 2013. For specific issues you may be facing in your environment, please post more details in Exchange forums (
    or contact Support (, who can help you with troubleshooting, collect the required information and help us track such issues.

  92. Stephen Frost says:

    Hi guys,

    Now that there is some "interaction" happening, is it possible for someone from MSFT to comment with some authority on this issue:…/sync-error-every-time-i-send-an-email

    It has been more than a year since I contacted Support about this and was told "yes, its a bug" and "it will be fixed" … but so far … nothing … and I know there are a LOT of people suffering from the same issue.

    At least two organisations I know are going to stick with Exchange 2007 until this is fixed.  My guess is that there are lots of others in the same boat.


  93. Weseeprogress says:

    After NINTEY comments here, MS announced when Exchange 2013 SP1 On-Premises will be released.

    We see progress here between the Exchange Engineer/Admin community & MS guys in this site.

    We can see that, you can listen to us (Customers worldwide) if we write you NINTEY comments here, so for that I will say, Thanks.

  94. Rhys says:

    With the announcement of SP1, we'll evaluate Exchange 2013 again in Mid 2014. Until then we'll continue rolling out Exchange 2010 SP3, and also migrating users from Office 365 to Exchange 2010 SP3 as they request it due to the instability/problems.

  95. @Stephen Frost – We're working on tracking down the current status of that bug.  Will share out authoritative status with you soon.

  96. Zoltan Erszenyi says:

    @Bharat Suneja, can you please elaborate on what you mean by "next release of Exchange Server"? To me it means NOT a service pack, a CU or hotfix but a VERSION UPGRADE from 2013 to 2016 (or whatever it will be called).

    In this economic climate businesses want stable and reliable products which they can learn, stick with, and rely on for years to come, and they don't have to re-skill their staff every 2-3 years to keep in business. They want to MAKE, not WASTE money. They don't want to constantly fight fires, because it costs them money.

    So, again, what existing business need isn't addressed in Ex2010/2013 which MS is working on already so hard to to plug in its next version release, that fixing current issues seems to be secondary? How about focusing on fixing the problems at hand first, stablising what you try to sell now? How about you stop pushing your customers into replacing what they've come to know with new things which are buggy and they don't know, so that they must focus more on learning and putting up with new technology that doesn't bring them any measurable benefits, and actually enable them to go about their business?

    Here is a business tip for you guys: Let's maintain well established legacy software for the more conservative while you also offer the latest, not necessarily greatest, for those who are happy to take risks? The world would love you! XP vs Vista/Win7/Win8 is a prime example.

  97. Hello all,

    3rd Post – It's nice to see some interaction here – the cynic in me would love to think that the SP1 announcement blog was added quickly to placate these comments….

    I think there needs to be a definition of time – ie what does near future, soon, early, as soon as possible all mean to Microsoft? It's a simple question and I'd expect Microsoft to be able to say. By the end of November or By end of 2013 or even – we do not have a time for release sorry – there's a lot of work to complete.

    This post and comments are getting old and i suspect that the SP1 announcement posts will get the attention away from this

    Hope you do a better job at communicating next time Microsoft

  98. Ridiculous says:


    "We're working on tracking down the current status of that bug.  Will share out authoritative status with you soon."

    It's been over a year. That's a completely unacceptable answer that you still don't know what the issues is or have a solution. Completely unacceptable.

  99. Marcel says:

    I think how you can read in this posts you should stop working on a new version (2016?) for a while and first fix all the issues in Exchange 2013 and bring back the features from 2010.

    After this is done, you can start to work on a new Exchange version.

  100. Stephen Frost says:

    @Jon … re: status update of Sync Errors bug … thanks, that is very much appreciated!

  101. Stephen Frost says:

    @Ridiculous … re: Sync Errors bug … yes, its been more than a year that I've been waiting, but others have been waiting a lot longer than that … I can wait a few more days for information quite happily, provided that the information is correct and trustworthy.  I still don't know whether the bug is in Exchange 2010, or in Outlook 2010, or even both apps.

    Most of the frustration is because its not a critical error.  Outlook complains because it tries to delete something which is in Outlook but which isn't in the Exchange Server.  If it was in the Exchange Server, Outlook would delete it (without an Error) and then it wouldn't be in the Exchange Server.  The end result would be the same: the email would NOT be in the Exchange Server.  So if the end result is the same, why throw an error in the first place.  It does my head in!

  102. ThommyG says:

    @Stephen Frost: I've seen this sync error (0-130) a lot with our customers whend doing migrations to Exchange 2010 and was asked very often how to fix this. The only answer I received from MS yet is "this error can savely be ignored". That's all I can say to my customers for over three years now and from my perspective the Exchange Team has absolutely no idea how to fix this, maybe not even know what causes this error. If they do, it's maybe something that cannot be fixed, otherwise there would be a fix to this, because it's an absolutely annoying issue, both for admins which are asked to fix it and for the end user. I hope this is not just ignorance.

  103. declan says:

    Everything about Exchange 2013 has screamed "Cloud" since the product was released.

    From the Web based admin console with it's low bandwidth two tone blue white colour scheme, reduced graphics, reduced wizards and the removal of the ability to display or copy the invoked PowerShell command, reduced functionality, but it looks and feels the same for on prem (Enterprise) and Cloud (Office 365)

    The integration in a hybrid deployment within the EAC is pretty seamless, but the impression I get is that the Enterprise Admin capabilities had to be dumbed down to match those available on offer to Office 365 customers.

    It comes over as a branding exercise., Office 365 and Exchange 2013 all look and feel the same, which is nice.

    Nice is missing the point I think, when it comes to the install base of MS Exchange.

    I'm like many people, I've been working with Exchange since way back, Version 5 in my case, and Exchange 2013 Admin is a step backwards.

    Not everybody is thrilled about the cloud, many are sceptical, a few are die hard opposed. Personally I think it's coming, like it or not, but I'd appreciate more honesty and less spin from Microsoft.

    "We're investing in cloud because that's where we see the revenue, so get with the program" would no doubt cause an outcry, but probably no more so that "We're excited to be putting our customers first by investing in Office 365"

    We don't all want Office 365.

    We want the features and functionality of Exchange 2013 with the Admin capabilities of Exchange 2010 on premises.

  104. @ThommyG, @Ridiculous, @Stephen Frost – I tracked down the status of the sync error bug. Stephen and Thommy, you are correct in how you characterized the bug: Outlook is basically spewing false positives about sync issues as it talks to Exchange. We know this creates work for admins who need to explain this to confused users. We understand your frustration that this has not been fixed; however as a non-critical error it has been cut from prior updates.  In response to your feedback, we’ve reopened the discussion about the bug, so it’s possible it may make it above the cut line in a future review, but for now the recommended workaround is to tell users to ignore the error unless they’ve encountered a problem deleting a specific item.

  105. Mad Max says:

    @Jon, you say " however as a non-critical error it has been cut from prior updates."

    To which I respond that it has been going on for a year. Constant sync errors on clients. It is 100% pure BS that you have not addressed the issue within an entire year. 100% pure BS.

    And then you come to this blog and tell us you are already working on a newer version. Well, if you'd just put that newer version on hold for a bit you'd have plenty of resources left to fix the bugs, errors, and problems you have still not fixed in your shipping product.

    100% BS that you are putting resources into any future version of Exchange while constant errors plague us.

    Thumbs down to the entire Exchange team.

  106. Stephen Frost says:

    @Jon … thanks for the update … I really, really hope the team reconsiders their position and fixes this … in both Exchange 2010 and 2013 (or in Outlook 2010/2013 if that's where the problem lies).

    To you guys it looks Trivial.  To end users, its an Error and requires Explanation.  You're creating lots of extra Work for thousands and thousands of sysadmins by not fixing this.  That makes it a Serious problem, not Trivial.

    All I can do is repeat what I've said earlier:  until this is fixed, every company I'm responsible for will remain on Office 2007 and Exchange 2007 … so by NOT fixing it, MSFT is losing money.  I'll bet you any amount of $$$ that I'm not the only sysadmin who is thoroughly sick of stuff like this not getting fixed.

    You make US look bad in front of our customers and end users.  THAT's why we get so bloody angry about it when simple stuff like this doesn't get fixed for year after year.

  107. Stephen Frost says:

    Sorry … I just want to make a further comment about this:

    "… for now the recommended workaround is to tell users to ignore the error unless they’ve encountered a problem deleting a specific item."

    That's just not an acceptable outcome.  Let me explain why.  To following that workaround, every user has to read every Sync Error message, including all the False Positives, just in case there is an occasional Genuine Delete Error reported in the Sync Issues.

    The hit to productivity for End Users would be Catastrophic.  Besides which, they are just not capable of accurately determining whether something is really Genuine Error or a False Positive.  

    The end result of THAT is that nobody pays ANY ATTENTION AT ALL to anything in the Sync Issues folder.  That, in turn, means that Genuine Errors are missed as all messages are being Ignored.

    Please communicate this to the team:  errors MUST be worthwhile and accurate, otherwise they get ignored.  Its NOT just a cosmetic problem, because the team is NOT taking into account End User Behaviour.

    Once we train End Users to Ignore Errors we are in Trouble.  That is the biggest reason why this should be fixed, and fixed quickly.

  108. @Everyone email subscribed to this thread asking about CU3.

    2013 CU3 has now been released, please see the new article at…/released-exchange-server-2013-cumulative-update-3.aspx

  109. Doug says:


    Your continued silence is disappointing.  Please plan on attending Tech-Ed in Houston and making yourself available for the Birds-of-a-Feather sessions.  Be prepared to field questions such as the ones below.

    Thank you.

  110. Doug says:

    …that is, questions such as the ones above, in this reverse-sort blog format.

  111. carl says:

    Are we ever going to get answers? Namely, when is the next version of Exchange expected and what are the new and improved features that are coming? Seems odd to drop a bunch of questions right at the first of the post that you never answer.

    There is a literal buttload of complaints raised here and all sorts of people are unhappy with Exchange. Is anyone going to answer these issues or is this being "under rug swept" and we should just all move to Office 365?

  112. Bharat Suneja [MSFT] says:

    @Carl: As indicated in the post:

    We expect the next on-premises version to be released according to our traditional release cadence (2-3 years after the previous version).

    We’ll share more details as we get closer to release.

    Note, this post listed some of the usual questions we get around this time
    (When’s SP1 coming? When’s the next version coming? What’s new in the next version?)
    , followed by an unusual one
    (will there be another version of Exchange Server?). This post addresses the latter question.

    Exchange 2013 SP1 was announced shortly
    after this post.
    Exchange 2013 CU3
    was also released shortly after that.

  113. carl says:


    >>We'll share more details as we get closer to release.<<

    Then what is the point of this post other than to confuse, inflame, and bewilder people? For a post titled "Exchange Server: The Road Ahead", it seems like you've done your damnedest here to avoid actually telling us what lies on the road ahead.

    >>>(will there be another version of Exchange Server?). This post addresses the latter question.<<<

    I see nothing in your reply or these posts that addresses that question. What's the timeline and what are you cooking up? It's a really easy, straightforward question that your Vice President himself asked in this post, but hilariously nobody can seem to answer clearly.

  114. PMP says:


    Then what is the point of this post other than to confuse, inflame, and bewilder people? For a post titled "Exchange Server: The Road Ahead", it seems like you've done your damnedest here to avoid actually telling us what lies on the road ahead.

    I guess Exchange Team is just buying time. As we all (others) know MS will not inform anything unless they are allowed to do so. I've been working with Exchange about 10 years and this (E2013) is the first version that has been a big disappointment form me personally and for many of my colleges. I haven't heard anyone saying something positive about the product. The sooner MS will announce next version of Exchange the better.

  115. Simon says:

    >>>(will there be another version of Exchange Server?). This post addresses the latter question.<<< So, this question will never be answered even after two months? Perry Clarke, you suck as a VP.

  116. Answers? says:

    No answers to the questions? Perry Clarke, you suck big time as a VP.

  117. Can ANYONE PLEASE ANSWER!!!!????!!!! says:

    What are you cooking up for the next version of Exchange? You’ve STILL never answered that question and it is 3 MONTHS later? This has to be the worst blog article ever published!!! Please finish writing the blog!!!

  118. Goodbye says:

    The answer is in the latest blog entry: We don’t want you anymore!

Comments are closed.