Outlook Anywhere users prompted for credentials when they try to connect to Exchange Server 2013 or Exchange Server 2016
Consider the following scenario:
- You are running Microsoft Exchange Server 2013 or Microsoft Exchange Server 2016 in a coexistence environment together with either or both Microsoft Exchange Server 2010 or Exchange Server 2007.
- Mailboxes in this environment connect through an Exchange Server 2013 Client Access server (CAS) or Exchange Server 2016 client access service.
- Users in this environment try to connect their Exchange Server 2010 or Exchange Server 2007 mailboxes by using the Outlook Anywhere feature.
This problem may also affect Outlook Anywhere connections to Exchange Server 2010 or Exchange Server 2007 legacy public folders or Offline Address Books (OAB).
Troubleshooting indicates that the affected users cannot connect directly to the legacy Client Access servers (CAS) by using Outlook Anywhere.
This problem occurs if the Exchange Server 2010 or Exchange Server 2007 servers that have the CAS role are running in Windows Server 2008 R2. This problem occurs because an incorrect flag is set in a global credential after the computer password for the CAS is changed. More information about this problem is included in the hotfix package that is mentioned in the "Resolution" section.
To resolve this problem, install the following update on all Exchange Server 2010 and Exchange Server 2007 CAS that are running in Windows Server 2008 R2:
3140410 Security update for Microsoft Windows to address elevation of privilege: March 8, 2016Note You must restart the computer after you apply this security update.
When this problem occurs, an error may be logged in the HTTP RPC Proxy logs at the following location:
C:\Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\RpcHttpThis log entry resembles the following:
Complete=PrepareServerRequest;,WebExceptionStatus=ProtocolError;ResponseStatusCode= 401;WebException=System.Net.WebException: The remote server returned an error: (401) Unauthorized. atSystem.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) atMicrosoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.<>c__DisplayClass1.nullb__0 ();HttpException=System.Web.HttpException (0x80004005): NegotiateSecurityContext failed with for host 'mail.contoso.com' with status 'InvalidToken' at Microsoft.Exchange.HttpProxy.KerberosUtilities.GenerateKerberosAuthHeader.
To work around this problem, configure the default application pool on all the 2010/2007 CAS to run under the Network Service identity instead of the Application Pool identity. This workaround is temporary.
To change the default application pool configuration, follow these steps:
- Start Internet Information Services (IIS) Manager.
- Click Application Pools, right-click DefaultAppPool, and then click Advanced Settings.
- Click Identity, and then click the Ellipses (…) button.
- Click the drop-down arrow, and then locate Network Service in the list under Built-in account.
- Right-click the Default application pool, and then click Recycle
Article ID: 2990117 - Last Review: 03/29/2016 01:55:00 - Revision: 4.0
Exchange Server 2016 Enterprise Edition, Exchange Server 2016 Standard Edition, Microsoft Exchange Server 2013 Service Pack 1, Microsoft Exchange Server 2013 Standard, Windows Server 2008 R2 Enterprise, Microsoft Exchange Server 2010 Enterprise, Microsoft Exchange Server 2007 Enterprise Edition
- kbsurveynew kbtshoot kbexpertiseinter KB2990117