Late last night we became aware of an issue with MS13-061 security update for Exchange Server 2013. Specifically, after the installation of the security update, the Content Index for mailbox databa...
Updated Jul 01, 2019
Version 2.0
Blog Post
On one hand we need to always update to the latest CU or service pack in order to maintain our support with Microsoft. However, all of the recent patches break things. For example, the latest CU2 patch appears to have broken OWA redirects and password resets in addition to a whole host of other bugs we are finding. Pulling the previous patch due to PF issues and then less than a week later another show-stopping bug. It's madness. Simply madness. And now we find out that Microsoft doesn't even test the patches internally first. Not even critical ones. Get out of town.
1.Is there a change planned to the upgrade cycle where we can have more time to test and iron out all these bugs? This forced N-1 upgrade support is just not sustainable with the amount of shoddy patches being released. We can't update our servers every quarter and watch things break.
2. Since TechNet is going away, how can we continue to test Exchange without having to pay over 6000? The free and/or online labs don't include Exchange 2003 or 2007 and you can't download them anymore, which is most of what my customers are upgrading from. We also cannot test any complicated scenarios. We can't even test forest trusts and certificates.So, how does the Exchange team envision people deploying Exchange if we can't download and test the software adequately?
Thank