###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 organization. The organization contains servers that have
Exchange Server 2010 and Exchange Server 2016 installed.
You establish a hybrid deployment between Exchange Server and Microsoft Office 365. Some users have onpremises mailboxes and personal archives in Exchange Online.
You discover that you are unable to use In-Place eDiscovery to search user mailboxes and Exchange Online
Archiving archives concurrently.
You need to recommend a solution to ensure that In-Place eDiscovery can search the mailboxes and the
personal archives concurrently.
What should you include in the recommendation?
A.
Auth authentication
B.
an organization relationship
C.
a retention policy
D.
the Mailbox Replication service (MRS)
eDiscovery in an Exchange hybrid deployment
In a hybrid deployment, which is an environment where some mailboxes exist on your on-premises Mailbox servers and some mailboxes exist in a cloud-based organization, you can perform In-Place eDiscovery searches of your cloud-based mailboxes using the EAC in your on-premises organization. If you intend to copy messages to a discovery mailbox, you must select an on-premises discovery mailbox. Messages from cloud-based mailboxes that are returned in search results are copied to the specified on-premises discovery mailbox. To learn more about hybrid deployments, see Exchange Server 2013 Hybrid Deployments.
To successfully perform cross-premises eDiscovery searches in an Exchange 2016 hybrid organization, you will have to configure OAuth (Open Authorization) authentication between your Exchange on-premises and Exchange Online organizations so that you can use In-Place eDiscovery to search on-premises and cloud-based mailboxes. OAuth authentication is a server-to-server authentication protocol that allows applications to authenticate to each other.
OAuth authentication supports the following eDiscovery scenarios in an Exchange hybrid deployment:
Search on-premises mailboxes that use Exchange Online Archiving for cloud-based archive mailboxes.
Search on-premises and cloud-based mailboxes in the same eDiscovery search.
For more information about the eDiscovery scenarios that require OAuth authentication to be configured in an Exchange hybrid deployment, see Using OAuth authentication to support eDiscovery in an Exchange hybrid deployment. For step-by-step instructions for configuring OAuth authentication to support eDiscovery, see Configure OAuth authentication between Exchange and Exchange Online organizations.
For step-by-step instructions for configuring OAuth authentication to support eDiscovery, see Configure OAuth authentication between Exchange and Exchange Online organizations.
1
0
In-Place eDiscovery in Exchange 2016
https://technet.microsoft.com/en-us/library/dd298021(v=exchg.160).aspx
1
0
Agree with A.
0
0
Added to in-place eDiscovery, O-Auth Authentication also enables, inplace archive amd Message Rights Management (MRM) features in a Hybrid deployment, to connect cloud based mailboxes from On-premises.
For Exchange 2013 CU5 and later, this is availed through Hybrid Configuration wizard itself.
0
0
However, certain Exchange 2013 features are only fully available across your organization by using the new Exchange OAuth authentication protocol.
The new Exchange OAuth authentication process currently enables the following Exchange features:
Message Rights Management (MRM)
Exchange In-place eDiscovery
Exchange In-place Archiving
https://technet.microsoft.com/en-us/library/dn594521(v=exchg.160)
0
0