Exchange Server 2010 Service Pack 2 rollup update 3 provides Exchange administrators with 42 bug fixes plus RPC...
client access cross-site connectivity changes that customers have waited for.
Rollup 3 (RU3) is the third straight fix-laden update since Exchange 2010 SP2 rollup update 1 dropped in February 2012. That makes 143 fixes in three Exchange 2010 SP2 updates. The large number of fixes for a seemingly stable and mature product still surprises many IT pros.
“I am continually amazed at how many bugs still exist,” said Mike Crowley, an Exchange MVP and enterprise infrastructure architect at Planet Technologies Inc., based in Germantown, Maryland. “But that just shows us how complicated Exchange Server really is.”
More Exchange Server-related news:
Some of the most important fixes released this week include remedies for five different Outlook Web App (OWA) 2010 bugs.
For one, prior to the update, OWA users could not log into a full mailbox.
“This is a denial of access to potentially critical information in email,” said Rob Sanfilippo, an analyst at Directions on Microsoft, a consulting firm based in Kirkland, Wash.” If a user can’t get into his mailbox via OWA, that’s a problem for the admin who has to get that access back.”
Sanfilippo also pointed to two other issues that, while seemingly small, caused unnecessary aggravation for Exchange admins.
Prior to rollup 3, Message Records Management retention policies that were applied to the junk email folder wouldn’t work when users manually moved email messages in Exchange Server 2010. Also, meeting requests bypassed the requirement for delegate approval and instead booked resource mailboxes automatically in Exchange 2010.
“Both of these issues fit into a class where you rely on Exchange to automate something for you, but it doesn’t. These simply aren’t things admins should have to worry about,” Sanfilippo said.
These specific fixes are certainly noteworthy, but the most interesting part of this update might be fix 2671128. In the rollup update notes, it is simply described to repair “RPC Client Access Cross-Site connectivity issues [that] occur in an Exchange Server 2010 environment.”
After applying Exchange 2010 RU3, customers’ mailboxes that are moved between Active Directory sites will have their profiles updated correctly. Also, admins can control whether to allow the cross-site RPC connectivity (default) or to force Outlook to use the RPC Client Access Server array in the same Active Directory site as the activated and mounted database, according to Ross Smith IV’s Exchange team blog.
“This seems to [actually] be a feature enhancement. It’s a good thing that customers have been asking about for a while,” said Crowley.
Let us know what you think about the story; email Site Editor Matt Gervais.
Dig Deeper on Microsoft Exchange Server 2010