###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###
You have an Exchange Server 2016 organization.
All users work from a main office and use Microsoft Outlook 2016.
You recently ran the Microsoft Office 365 Hybrid Configuration Wizard and moved most of the user mailboxes
to Exchange Online. A network administrator reports an increase in the amount of outbound SMTP traffic from
the network.
You need to reduce the amount of bandwidth utilization for the outbound SMTP traffic.
What should you do?
A.
From the Exchange Server organization, create a Receive connector that uses the IP address of
Exchange Online as a remote range.
B.
From the public DNS zone, modify the MX record to point to Exchange Online.
C.
From the public DNS zone, modify the SRV record to point to Exchange Online.
D.
From the Exchange Server organization, create a Send connector that uses Exchange Online as an
SMTP smart host.
How can MX record changing have any effect to outbound SMTP traffic? It directs inbound SMTP traffic to EOP
If the MX records still points to on-prem, the email will be send over the internet to Office 365 (Hence additional outgoing mail).
If you point to the cloud, then this behavior is altered that you have more incoming mail from Office 365.
As the question provide: Most of the users are in the cloud.
This will lower the outgoing mail flow, which is the only thing asked at this time. Because the on-premise server doesn’t need to send all the mail for the users to the cloud.
The key is to “lower the bandwidth utilization” for outbound SMTP. The MX record change reduces the bandwidth as emails for users in the cloud would no longer be sent to on-prem before being routed to the cloud. This would remove the bandwidth used for this in and out traffic, and as such more bandwidth is released for the outbound SMTP traffic and outbound SMTP traffic is also reduced.
I guess in this scenario look like this https://postimg.org/image/jikr08dxx/
Original from
https://mva.microsoft.com/en-US/training-courses/migrating-to-exchange-online-8407?l=dlHiIoJz_8404984382
In a Hybrid environment (which is the case for this scenario), you can point the MX record to either on-premise or Exchange Online (O365). Where you point the MX record, will determine where the INBOUND emails from the internet will arrive first.
Let’s say the MX is pointed to on-premise (as per this question). If an inbound email from the internet is destined for an Exchange Online mailbox, then that email will arrive on-prem first, then be routed from on-prem outbound to Exchange online. This routing involved from on-prem to Exchange online is what the question is asking you to fix, as the outbound SMTP traffic for Exchange Online is too much load the bandwidth.
Now, keep in mind that if the email destined for the Exchange Online mailbox is replied to, it will go outbound directly from Exchange Online to the internet, as this is the shortest route to the destination. Exchange Online mailboxes does NOT depend on the availability of on-prem Exchange servers for outbound email. The exception to this is if Centralized Transport is used.
Managing Changes to MX Records and Incoming Email Traffic
http://practical365.com/exchange-server/changing-mx-records/