###BeginCaseStudy###
Topic 3, Contoso Ltd,
Overview General Overview Contoso. Ltd. is an international company that has 3,000 employees.
The company has sales, marketing, research, and human resource departments.
Physical Locations
Contoso has two main offices. The offices are located in New York and Chicago. Each moffice has a data center.
The New York office uses a network subnet of 10.1.0.0/16. The Chicago office uses a mnetwork subnet of
10.128.0.0/16.
The offices connect to each other by using a WAN link. Each office connects directly to the Internet.
Existing Environment
Active Directory The network contains an Active Directory forest named contoso.com. The forest mcontains a
single domain. All domain controllers run Windows Server 2012 R2. The forest mfunctional level is Windows
Server 2012 R2.
The forest contains six domain controllers configured as shown in the following table.
The forest is configured as a single Active Directory site.
Active Directory administrators manage the Active Directory schema. Exchange Server madministrators do not
have access to modify the schema.
Contoso has deployed Active Directory Rights Management Services (AD RMS).
Current Business Model
Contoso partners with a company names Fabrikam. Inc. on manufacturing initiatives. The partnership between
Contoso and Fabrikam requires that both companies share confidentialm information frequently.
Requirements
Business Goals
Contoso plans to install Exchange Server 2016 to provide messaging services for its users.
It must be as easy as possible for the users at Contoso to share free/busy information with mthe users at
Fabrikam.
As much as possible Contoso plans to minimize the costs associated with purchasing hardware and software.
Planned Changes
Contoso plans to implement the following changes before installing Exchange Server 2016:
Install hardware Network Load Balancing (NLB) in the New York and Chicago offices.
Implement Microsoft Office Online Servers in the New York and Chicago offices.
Provide Contoso users with company-approved tablets.
Planned Messaging Infrastructure
You plan to create an Exchange Server 2016 organization named Contoso. You plan to deploy seven servers
that will have Exchange Server 2016 installed. The servers will be configured as mshown in the following table.
All of the servers will be members of a database availability group (DAG) named DAG01.
Client Access Requirements
Contoso identifies the following client access requirements for the planned deployment:
Users must be able to configure their tablet to synchronize email by using Autodiscover.
Users must be able to access the Exchange Server organization by using the following names:
Mail.contoso.com
Autodiscover.contoso.com
Users must be able to access Outlook on the web internally and externally from their tablet.
Users must be able to access Office Online Server by using the URL of office-online.contoso.com.
Security Requirements
Contoso identifies the following security requirements for the planned deployment:
Exchange Server mailbox databases must be encrypted while at rest.
Users must be prevented from using Outlook on the web while they are offline.
Contoso users must be able to share Calendar details with approved external domains only.
Email messages sent to the users in the fabrikam.com SMTP domain must be encrypted automatically.
Whenever possible, client computers must be directed to the same Exchange server for log collection.
Users must be able to access their mailbox by using Exchange ActiveSync on the company approved tablets
only.
Email messages sent from the users in the human resources department of Contoso must be protected by
using AD RMS. regardless of the mail client.
Availability Requirements
Contoso identifies the following high-availability requirements for the planned deployment:
Servers must be able to complete a restart without administrative intervention.
The network load balancer must be able to probe the health of each workload.
If a data center fails, the databases in the other data center must be activated automatically.
Redundant copies of all email messages must exist in the transport pipeline before and after mdelivery.
Email messages must be made highly available by the Exchange Server organization before and after delivery.
If you manually mount the databases following the data center failure, the databases in the failed site must be
prevented from mounting automatically.
###EndCaseStudy###
HOTSPOT
You have an Exchange Server 2010 organization.
You plan to upgrade to Exchange Server 2016.
You have two active directory sites configured as shown in the following table
You have five servers configured as shown in the following table.
You have three users who have mailboxes configured as shown in the following table.
Answer: 
I’ve got the feeling that this question contains errors.
When a user connects to a 2016 Mailbox server and he has a mailbox on a 2010 Mailbox server, he will be proxied to a 2010 CAS server and the 2010 CAS server will connect to the 2010 Mailbox server.
When a user connects to a 2016 Mailbox server and he has a mailbox on that same server (user 3), he will already be on the correct server and won’t need to be redirected or proxied to another CAS server.
So, the answer would be:
User1: No (because he will be proxied)
User2: No (because he will be proxied)
User3: No (because he is already connected to his Mailboxserver)
https://blogs.technet.microsoft.com/exchange/2015/10/26/client-connectivity-in-an-exchange-2016-coexistence-environment-with-exchange-2010/
Note:Non-Internet Facing AD Site, simply means any Active Directory site containing Exchange servers whose virtual directories do not have ExternalURL property populated.
So, if Brussels is Non-Internet facing site, why ExternalUrl is populated.
In this case:
– If user1 use https://mail.contoso.com/owa, she/he will be redirected to https://mail.brussels.contoso.com/owa (CAS01) => Yes
– If user2 use https://mail.contoso.com/owa, she/he will be redirected to https://mail.brussels.contoso.com/owa (CAS01, not CAS02) => No
– If user3 use https://mail.contoso.com/owa, she/he will be proxied to EX03 => No
Mahoney you are right.. but the user2 will be a proxied from EX03 to CAS02 (not redirect to CAS01). anyway the answers are:
– Yes
– No
– No
Agree with your answers but disagree with your explaintion. CAS02 located in New York site not in Brussels!!! Any request to mailbox on EX01 and EX02 will be proxied to CAS01 because it’s located on site in Brussels. CAS02 will not participated in this scenarion. Read artical that Mahoney provided again
Agree with Mahoney:
Yes
No
No
With more reflexion, i’m agree with Marco:
User 1 can’t be redirected as the Brussels site is not facing Internet! 🙂
So the external URL on CAS1 can’t be used.
Hence, user1 will be proxied, not redirected.
NO (proxied to CAS01)
NO (proxied to CAS01)
NO (Already connected to EX03)
The term, Internet Facing AD Site, simply means any Active Directory site containing Exchange servers whose virtual directories have the ExternalURL property populated. Similarly, the term, Non-Internet Facing AD Site, simply means any Active Directory site containing Exchange servers whose virtual directories do not have ExternalURL property populated.
Read artical provided by Mahoney. Answers in this topic is Yes, No, No
Sam is right, The term Exchange considers internet facing by the External Url definition on the virtual directory, not whether you expose your servers to internet.
Mahoney is correct, its redirection, not proxy.
User 1 – Service Discovery-> Remote-Brussels Site/Exchange 2010—- Cross site Silent redirection (SSO) to CAS01 defined External URL
USer 2 – Service Discovery-> Remote-Brussels Site/Exchange 2010—- Cross site Silent redirection (SSO) to CAS01 defined External URL. CAS02 has no role as there is no Exchange 2010 Mailbox server in New York Site.
User 3 – Service Discovery-> Local-New York Site/Exchange 2016— Local proxy within Exchange 2016 mailbox server.
Answers are
Yes
No
No
….
Thanks, this made it clear for me.