###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###
DRAG DROP
You have an Exchange Server 2016 organization. The organization contains two Mailbox servers.
You have a database that is replicated to both servers. The database contains 500 mailboxes. You add new
volumes to the Mailbox servers.
You need to move all of the mailbox data to the new volumes. The solution must meet the following
requirements: Ensure that multiple copies of the mailbox data are available at all times.
Minimize downtime for the mailbox users.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.
Answer: 
The question demands that: “multiple copies of the mailbox data are available at all times”.
The given answer is incorrect.
I think the correct answer should be:
Create a new database
Create replicated database copies
Move the mailboxes
3
0
You are correct Marco.
0
0
Agree with you. Move database = downtime
0
0
Why must you create a new database? Why can’t you create new database copies on the new disks and activate one of the new database copies? Then remove the other database copies, of course.
0
0
marco is wrong
https://technet.microsoft.com/en-us/library/dd979782(v=exchg.160).aspx
answers are correct
0
1
Aerone you are wrong. Your link say:
To perform the move operation, the database must be temporarily dismounted, making it inaccessible to all users. If the database is currently dismounted, it isn’t remounted upon completion.
To perform the move operation, replication for the database must be disabled for all copies. It’s not enough to suspend replication; you must disable it by using the Remove-MailboxDatabaseCopy cmdlet to remove the database copies.
That procedure doesn´t match with requirements.
1
0
REMOVE ALL REPLICATED
MOVE DATA BASE
CREATE REPLICATED DB copies
0
1
How can you “Ensure that multiple copies of the mailbox data are available at all times” (requirement), if you first “remove all of the replicated database copies”?
I wonder what we should answer if we don’t have “Move the mailboxes” option..
1
0
To perform the move operation, the database must be temporarily dismounted, making it inaccessible to all users. This doesn’t match the availability requirement.
Marco is right.
0
0
The tech note that Aerone provided states:
“Remove all mailbox database copies for the database being moved. After all copies are removed, preserve the database and transaction log files from each server from which the database copy is being removed by moving them to another location. These files are being preserved so the database copies don’t require re-seeding after they have been re-added. Move the mailbox database path to the new location.” Thus, it seems Remove, move and create replica is the right answer.
0
1
I agree with Marco, but let’s check the reguirements vs given answers.
Requirements:
R1 Multi copies at any given time.
R2 Minimize downtime for the user.
======================================
Answers provided:
A1. Remove all copies of the database copies.
A2. Move the database
A3. Create replicated database copies.
=======================================
A1: So no more copies are availible, because you remove ALL copies in the answer and this in violation with statement R1.
A2: Missing the step of dismounting the database. Which results in long downtime for the users, because the database move is always preformed offline.
A3: First two are not matching the requirement.
=============My Answer=================
M1: Create new database, placed on the new disks. Not impacting the user.
M2: Create Multiple copy’s of the database. Which match with R1. Multi copies are availible.
M3: Move mailbox. This match R2. All Exchange 2016 mailbox move’s are online and can be done, will the user is working and has minimal impact when the switch is made between databases.
I also though this was the way to go by Microsoft and moving the database offline as last resort.
3
0
Could the answer actually be
1. Create new database
2. Mount database
3. Create new database copies
As you have to have a mounted database before creating copies. As the question already states you need to ‘move’ mailboxes already and the above are the steps before you do the move.
Their answers are so tricky!
1
0
Notice the “Minimize Downtime”. In Microsoft term means that it can be down.
0
0
all according to https://technet.microsoft.com/en-us/library/dd979782(v=exchg.160)
“To perform the move operation, replication for the database must be disabled for all copies. It’s not enough to suspend replication; you must disable it by using the Remove-MailboxDatabaseCopy cmdlet to remove the database copies.”
Remove all mailbox database copies for the database being moved. For detailed steps, see Remove a mailbox database copy. After all copies are removed, preserve the database and transaction log files from each server from which the database copy is being removed by moving them to another location. These files are being preserved so the database copies don’t require re-seeding after they have been re-added.
Move the mailbox database path to the new location. For detailed steps, see Move a mailbox database path.
importantImportant:
During the move operation, the database being moved must be dismounted. Until the move is complete, this process will cause an interruption in service and an outage for all users with mailboxes on the database being moved. After the move operation completes, the database is automatically mounted.
Create the necessary folder structure on each Mailbox server that previously contained a passive copy of the moved mailbox database. For example, if you moved the database to C:\mountpoints\DB1, you must create this same path on each Mailbox server that will host a mailbox database copy.
After creating the folder structure, move the passive copy of the mailbox database and its log stream to the new location. These are the files that were left from and preserved after Step 3. Repeat this process for each database copy that was removed in Step 3.
0
0
I agree with Exchanger!!
Create a new Database
Mount the new Database (since the option is given here)
Create DB replicas (must need a mounted DB)
Once these are done, Mailbox moves are online which can happen next.
1
0
I say :
Create a new database
Create replicated database copies
Move the mailboxes
Those of you who are saying “To perform the move operation, replication for the database must be disabled for all copies. It’s not enough to suspend replication; you must disable it by using the Remove-MailboxDatabaseCopy cmdlet to remove the database copies.”:
You are refering to moving the DATABASE…not moving the Mailboxes (which is the answer)
To move a MAILBOX this can be done with the databases online with almost no downtime for the user.
0
0
exchanger is correct
Could the answer actually be
1. Create new database
2. Mount database
3. Create new database copies
As you have to have a mounted database before creating copies. As the question already states you need to ‘move’ mailboxes already and the above are the steps before you do the move.
Their answers are so tricky!
0
0
Besides, part of that new 104Q 70-345 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpck5vRk5XUVFQb00
Best Regards!
0
0
This the important bit of this question: you want the initial database to maintain its high availability during this migration and also minimize user downtime. With that, you cannot remove any database replicas and you certainly can’t dismount anything.
In a production environment, I would do it like this:
1) create a new mailbox database
2) mount it… otherwise we can’t work with it
3) create database copies before moving anything so we have redundancy
4) start moving mailboxes in batches, maybe during OOH
1
0
The real problem is the present of the mailbox in production. Therefore as it is describe in this article, is necessary first create the db:
https://practical365.com/exchange-server/moving-an-exchange-server-2016-mailbox-database/
“A mailbox database can be moved, but before you proceed consider that the move requires the database to be dismounted and taken offline, so it will not be accessible by your mailbox users during the move. This is fine if the server has just been set up and there are no mailboxes on it, but if you’re moving a database with active mailbox users a better option would be to create a new database on the new volume and perform mailbox moves (which are non-disruptive to end users)”
0
0