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? ...
Updated Jul 01, 2019
Version 2.0
Blog Post
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?