Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

Symptoms

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.

↑ Back to the top


Cause

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.

↑ Back to the top


Resolution

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

↑ Back to the top


More Information

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

↑ Back to the top


Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2671128
Revision : 1
Created on : 1/7/2017
Published on : 6/5/2012
Exists online : False
Views : 326