This week the Microsoft Exchange team released the second rollup update for Exchange Server 2010 Service Pack 2...
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.
with a significant number of fixes.
The first Exchange 2010 Service Pack rollup -- released in February -- contained 58 fixes. This update includes 43 more.
Despite the large number of fixes, one analyst said that Exchange administrators shouldn’t be alarmed.
“If you look at the numbers, they seem surprising and worrisome. But look at the fine details, these seem to be mostly low priority bugs,” said Rob Sanfilippo, an Exchange analyst with Directions on Microsoft, an independent analysis firm based in Kirkland, Wash.
As the number of users accessing email and Exchange information via tablets and smart phones grows daily, making certain OWA and ActiveSync function properly is important to every organization.
“OWA is becoming increasingly critical and most devices -- like iPads and iPhones -- rely on ActiveSync,” Sanfilippo said.
One important OWA fix, detailed in KB article 2635223, clears up an issue where a hidden user is still displayed in the organization information of the OWA 2010 address book. This could lead to privacy issues.
Another fix remedies a problem where users could not log onto OWA 2010 when an Exchange 2010 client access server (CAS) acts as proxy for an Exchange 2007 CAS that’s not connected to the Internet.
Additionally, ActiveSync users can now access mailboxes inside Exchange Server 2010 forest.
Exchange 2010 SP2 RU 2 crash fixes
The update also includes three crash fixes, two of which apply to the edge transport server:
- 2681464: An EWS application crashes when it calls the GetStreamingEvents operation in an Exchange Server 2010 environment.
- 2693078: The EdgeTransport.exe process crashes in Exchange 2010.
- 2696857: The EdgeTransport.exe process crashes without sending an NDR message when sending a message to a distribution group in Exchange Server 2010.