The latest Exchange Server 2010 update dropped this week, providing 20 more bug fixes and further solidifying the product as companies prepare for its coexistence with Exchange 2013.
The Exchange team has released Exchange 2010 SP2 rollup update 5 v2. We've updated links on all fixes and where to download RU 5 v2 at the end of this article.
For example, RU5 fixes an issue where Exchange 2010 would unexpectedly choose a random public folder server if the user's default public folder server was unavailable.
More on Exchange 2013 release
Exchange Server 2013 preparation checklist
"The public folder database selection logic will be a large help to organizations trying to control bandwidth during the difficult migration process to Exchange 2013 public folders," said Devin Ganger, a messaging architect and consultant based in Seattle.
Additionally, RU5 stops Store.exe crashes on Exchange 2010 mailbox servers if virus-scanning API-based (VSAPI) antivirus software is installed.
"This shows that Microsoft made the right call removing VSAPI in [Exchange] 2013," said Michael Van Horenbeeck, a technology consultant with Xylos, an information and communication technology services provider and Microsoft partner in Belgium.
What's new in Exchange 2010 SP2 RU5
Coexistence aside, there are several other important fixes in the latest Exchange 2010 update. One is a database availability group (DAG) stability fix, which ensures a DAG doesn't lose quorum if a router or switch issue occurs.
"I'm hoping this fix will help resolve remaining stability issues with DAGs running in virtual environments," Ganger said. "Mismatches in network configurations cause slight delays in virtual network switch operation, and Exchange 2010 DAGs in virtual environments are sensitive to this disruption."
Two fixes will be important for companies that use Managed Folders. They both remedy issues where items unexpectedly remain in the Recoverable Items folder.
Organizations that run Outlook in online mode should also take note. One fix stops declined meeting requests from reappearing on users' calendars, and another halts the ambiguous "the operation failed" error message after a user opens a saved message from the Drafts folder and attempts to send it.
Let us know what you think about the story; email Site Editor Matt Gervais.