Outlook Anywhere clients cannot connect to a CAS server after you apply Exchange Server 2010 SP2 RU3
- A Microsoft Exchange Server 2010 organization has two sites.
- Outlook Anywhere is enabled on the Client Access (CAS) servers in Site A.
- The CAS servers in Site A are exposed to the Internet.
- Outlook Anywhere is enabled on the CAS servers in Site B.
- The CAS servers in Site B are not exposed to the Internet.
- You install Microsoft Exchange Server 2010 Service Pack 2 (SP2) update Rollup 3 (RU3).
RopHandler: Logon: [RopExecutionException] The client should use Outlook Anywhere and RpcClientAccess server from site Site B to access the mailbox.
Note CAS servers in other sites will not accept an RPC connection request if there is an endpoint that is Outlook Anywhere enabled in the same site as the mailbox. Additionally, the client profile is updated.
Method 1: Disable Outlook Anywhere on CAS servers that are not exposed to the Internet
Note We recommend that you use this method to resolve the issue that is described in the "Symptoms" section.
To resolve this issue, disable Outlook Anywhere on CAS servers that are not exposed to the Internet. After you disable Outlook Anywhere on CAS servers that are not exposed to the Internet, clients can connect to a CAS server in a different site.
Method 2: Disable preferred site enforcement
To resolve this issue, disable preferred site enforcement. To do this, create the following DWORD registry value:
Value Name: EnablePreferredSiteEnforcement
Data Type: REG_DWORD
Note After you set the EnablePreferredSiteEnforcement value to 0, a CAS server will accept connection requests from any site and not try to redirect the request to a different server.
After you install Exchange Server 2010 SP2 RU3, Exchange Server tries to redirect connection requests and update the user profile intelligently. This can result in better performance and increased availability.
Article ID: 2725008 - Last Review: 08/07/2012 02:29:00 - Revision: 2.0
- kbsurveynew kbprb kbtshoot KB2725008