The Exchange team has released rollup 5 for Exchange 2010 Service Pack 1, but Exchange administrators won’t be...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
quick to install this update following Microsoft’s recent product release gaffes.
In late July, the Exchange team re-issued update rollup 4 for Exchange 2010 Service Pack 1 (SP1). The re-release stemmed from customer complaints that when using Outlook to move or copy a folder, subcontents and content for that folder were deleted. Microsoft explained on its Exchange Team blog what went wrong and how it would avoid further mishaps.
Less than a month later, update rollup 5 is here with fixes for even more customer-reported and internally discovered Exchange 2010 SP1 bugs.
Even though RU 5 includes important fixes, many Exchange administrators are hesitant to install the update. “We’ve all been burned twice now in recent history, so I will not be advising my customers to upgrade until some time has passed,” said Mike Crowley, an Exchange MVP and Enterprise infrastructure architect at Planet Technologies, Inc.
But others are confident that Microsoft has done some additional quality control to prevent another recall. “You might be more certain that this one is a solid release if these previous problems didn’t happen,” Rob Sanfilippo, an analyst with the Kirkland, Wash.-based Directions on Microsoft. “There’s been a lot more focus on getting a quality rollup out there.”
Included in the rollup are fixes for two role based access control problems. Before the update, assignees were able to run the Add-ADPermission command on an Exchange 2010 server outside their role assignment group. Also, assignees could unexpectedly manage certificates outside their assignment group.
Several Outlook Web App 2010 problems were resolved as well. The Exchange team specifically called out an issue of OWA zip-downloads not working for some messages due to invalid characters in the subject line.
Additionally, for those running Forefront Security for Exchange Server, you must still first disable Forefront, install the update, then re-enable ForeFront, much to Crowley’s chagrin. “This seems like something Microsoft could obviously include in [its] own code,” he said.
Update Rollup 6 for Exchange Server 2010 SP1 is scheduled to release in October and Service Pack 2 is due out in late 2011.
Let us know what you think about the story; email Matt Gervais.