[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] Released: Update Rollup 5 for Exchange 2010 SP1 - THE OFFICIAL BLOG OF THE SBS DIVA
Wed, Aug 24 2011 22:24 bradley

Released: Update Rollup 5 for Exchange 2010 SP1

Released: Update Rollup 5 for Exchange 2010 SP1 - Exchange Team Blog - Site Home - TechNet Blogs:
http://blogs.technet.com/b/exchange/archive/2011/08/23/released-update-rollup-5-for-exchange-2010-sp1.aspx

In the comments of that blog post...  For those keeping track.. the bug introduced in v4 is not fixed in v5

"With regard to the ability to recover a deleted public folder, this fix was not included in RU5 as further testing revealed a problem with the identified fix. We are still working on a resolution to this issue and it will be included in a future Rollup or Service Pack when it resolves the issue satisfactorily and has been fully validated."

Announcing the re-release of Exchange 2010 SP1 Rollup 4 - Exchange Team Blog - Site Home - TechNet Blogs:
http://blogs.technet.com/b/exchange/archive/2011/07/27/announcing-the-re-release-of-exchange-2010-sp1-rollup-4.aspx

Strike that.  If you install the update rollup 4 v2 (the one on WSUS and MU) you don't get the bug introduced into your Exchange environment.  This is only of importance if you installed rollup 4 v1 manually.  If you did not do that, you don't need to worry about any bug introduced behavior.

Filed under:

# re: Released: Update Rollup 5 for Exchange 2010 SP1

Thursday, August 25, 2011 1:53 AM by Paul Crosbie

I have lost total confidence in the Exchange Team.  There is no way I am going to install one of their updates until sufficient time has passed for them to 'pull it' and put out a working version.  While the update may fix an issue I am having I'm not prepared to introduce another bug that then can't be fixed.  This is Exchange we are talking about - the software that our entire business hinges on.

# re: Released: Update Rollup 5 for Exchange 2010 SP1

Thursday, August 25, 2011 2:09 PM by Pete P

Remember manual installation requires opening a command line as Administrator and running the update from there.