RPC Client Access Cross-Site connectivity issues occur in an Exchange Server 2010 environment

Article ID: 2671128 - View products that this article applies to.
Expand all | Collapse all

On This Page


You experience one of the following RPC Client Access Cross-Site connectivity issues in a Microsoft Exchange Server 2010 environment.

Issue 1

Assume that you move mailboxes from a database to another database that is in a different datacenter. However, the Microsoft Outlook profile on the target RPC Client Access endpoint is not updated unless the source RPC Client Access endpoint is unavailable.

Issue 2

Assume that a cross-site database failover event occurs. In this situation, Outlook does not set up a direct connection from the Client Access Servers (CAS) array in the first datacenter to the mailbox that hosts the active copy in the second datacenter.


These issues occur because RPC Client Access now connects directly to the destination mailbox store. Additionally, the Outlook client ignores information from the Autodiscover component when an endpoint is reachable.


To resolve these issues, install the following cumulative update:
2685289 Description of Update Rollup 3 for Exchange Server 2010 Service Pack 2


For more information about RPC Client Access, go to the following Microsoft website:
General information about RPC Client Access


Article ID: 2671128 - Last Review: June 5, 2012 - Revision: 2.0
  • Microsoft Exchange Server 2010 Service Pack 2, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2671128

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com