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
@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.