Microsoft re-releases another Exchange update rollup

Leave a comment

August 3, 2011 by Rakesh Boraiah

For the second time this year, Microsoft had to re-issue a recent service pack rollup update to correct a problem in the original release, further frustrating the Exchange community.

In late March, Microsoft re-released Exchange Server 2007 SP3 update rollup 3 to correct an issue that could have potentially led to database corruption. This time, Exchange Server 2010 SP1 update rollup 4 was removed from the download center three weeks after its June 22 release. The rollup was recalled after customers reported that when using Microsoft Outlook to move or copy a folder, subfolders and content for that folder were deleted.

Kevin Allison, general manager for Exchange Customer Experience, originally stated on the Exchange team blog that this issue would be fixed in Exchange 2010 SP RU 5, scheduled to drop in August. But Exchange 2010 SP1 RU 4 was re-released this week with extensive information as to what caused the problem. The Exchange Team describes the re-release as “functionally the equivalent of Exchange 2010 SP1 RU 4 and the interim update of knowledge base article 2581545.”

As expected, many in the Exchange community were frustrated that Microsoft released another rollup update with code problems.

“Back-to-back recalls of updates may cause companies to wait longer than they should to update their systems. This can be disruptive for business,” said Tom Phillips, consultant at TGPhillips Inc. in Allen, Texas.

Unlike the Exchange 2007 SP3 RU 3 re-release, Microsoft quickly owned up to everything that went wrong with the Exchange Server 2010 SP1 update rollup 4 release. On the Exchange Team blog, Allison explained what triggered the recall and why their initial testing failed. He also shared what the team is doing to prevent mishaps like this from happening in the future.

“For Microsoft to recall, fix and then explain a problem is huge,” Phillips said. “It shows that they’re re-evaluating testing procedures and seriously looking to avoid this kind of problem in the future.”


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: