Announcing the Re-release of Exchange 2010 Service Pack 1 Update Rollup 3 (V3)

@ConcernedFan-- I couldn't agree more! Historically, the Exchange product has been the poster child for Microsoft software. As an administrator, we have had the luxury of knowing that Microsoft has always had the best and brightest working on this product. I can remember the excitement of moving an organization from Novell Groupwise to Exchange 2003!

However, as you point out..the good ole days of having a solid product and confidence in product updates has dropped tremendously. I would have never thought that we would see the day that the Exchange product would experience such a black eye as it did over the past few weeks. Updates for two different product versions caused HUGE inconveniences for thousands of users worldwide!

Microsoft should realize that many organizations, especially large ones, have very closely monitored change control procedures. It's not as simple as just uninstalling a bad update. To further complicate the issue, if that particular rollup fixes an issue that we have been waiting for, you have a dilemma. Do you uninstall the update from multiple servers..reboot..install an interim update..reboot....only to have to schedule ANOTHER maintenance window to uninstall the interim update..reboot...install new rollup and reboot?

Finally, management is asking for an analysis of the entire situation. While I can provide the Exchange Team blog postings, that doesn't really satisfy "How was this allowed to happen in the first place?" question. Even opening a ticket with Microsoft Professional Support provided LESS information than was available via this website. It's like the Tier 1 technicians do not even read this blog...even after specifically sending them the link.

Sorry for the long post. Just wanted to provide some constructive feedback to the powers that be.