A company named Fabrikam, Ltd. has an Exchange Server 2013 organization that contains two
servers.
The servers are configured as shown in the following table.
You configure the internal and external namespaces named mail.fabrikam.com and
autodiscover.fabrikam.com to point to EX2.
You configure Outlook Anywhere on EX1 as shown in the following table.
You configure Outlook Anywhere on EX2 as shown in the following table.
You need to ensure that all of the users on EX1 can connect to their mailbox by using Microsoft
Outlook from the Internet.
What should you do?
A.
Change the authentication settings of EX1.
B.
Disable IPv6 on EX1.
C.
Change the authentication settings of EX2.
D.
Disable Outlook Anywhere on EX1.
A/C- You must ensure that client authentication on all CAS servers, including Exchange 2013
and Exchange 2007, is set to Basic and the Internet Information Services (IIS) authentication
method includes NTLM.
D- during coexistence with Exchange 2013, you must enable Outlook Anywhere on all Exchange 2007 servers.
“B” – https://support.microsoft.com/en-us/kb/2794253
0
0
Outlook Anywhere does not work if IPv6 is enabled on an Exchange Server 2007 multi-role server
0
0
Consider the following scenario:
so the answer is B.explain:
You have a member server that has the Microsoft Exchange Server 2007 Client Access role and the Mailbox role installed.
The server is not a global catalog server.
Internet Protocol version 6 (IPv6) is enabled on the server.
In this scenario, Outlook Anywhere does not work. For example, when you try to create a Microsoft Outlook profile in the environment, Outlook does not resolve the namespace.
Notes
This issue does not occur in single-role Exchange Server 2007 deployments where the member server has only the Client Access Server role installed.
This issue also occurs when you use Outlook Anywhere externally in an Exchange Server 2007 and Exchange Server 2013 coexistence environment.
0
0