You have an Exchange Server 2010 organization.
Users access Outlook Web App by using the name mail.contoso.com.
You deploy Exchange Server 2013 to the existing organization.
You change the DNS record of mail.contoso.com to point to an Exchange Server 2013 Client Access server.
The users report that they can no longer access their mailbox from Outlook Web App.
The OWA virtual directory in Exchange Server 2010 is configured as shown in the exhibit. (Click the Exhibit
button.)
You need to ensure that the users on Exchange Server 2010 can access Outlook Web App.
Which setting should you change?
A.
WindowsAuthentication
B.
FormsAuthentication
C.
LegacyRedirectType
D.
FailbackUri
Explanation:
Windows Authentication (NTLM) needs to be enabled on the Exchange 2010 Client Access Server to enable
the Exchange 2013 Client Acess Server to proxy connections.
Exchange Server Deployment Assistant
Enable and configure Outlook Anywhere
To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2007 and Exchange
2010 servers, you must enable and configure Outlook Anywhere on all of the Exchange 2007 and Exchange
2010 servers in your organization. If some Exchange 2007 or Exchange 2010 servers in your organization are
already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange
2013. When you use the steps below to configure Outlook Anywhere, the following configuration is set on each
Exchange 2007 and Exchange 2010 server:
The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
Client authentication, which is used to allow clients like Outlook 2013 to authenticate with Exchange, is set to
Basic.
Internet Information Services (IIS) authentication, which is used to allow Exchange servers to communicate, set
to NTLM and Basic.