Professional Documents
Culture Documents
18 COMMENTS SHARE
Get expert tech
reports and guides
for FREE!
Email address
CO U N T M E I N !
LATEST PODCAST
If you would like to read the other parts in this article series please go to: TechGenix Xtreme
Blockchain expl… Share
Migrating a small organization from Exchange 2010 to Exchange 2016 18 COMMENTS SHARE
(Part 5)
Migrating
SECTIONS
the Pilot
TECH NEWS
Group
TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT
Before migrating mailboxes en-mass to Exchange 2016, it’s important to Get a free copy of
the new
validate that you’ve had an opportunity to identify any issues that using SolarWinds
The first method applies if you have created equivalent databases to match
FOLLOW US
your source Exchange 2010 environment. For each database, you can queue
up mailboxes to be moved using the following command:
Get-Mailbox -Database <Database> | New-MoveRequest -TargetDatabase<Database_E2016
18 COMMENTS SHARE
If you are using traditional backups on your Exchange 2016 server then
take into account the impact of log file usage when determining the batch
sizes.
When a mailbox is moved, log files consuming the same amount of space as
the mailbox itself are generated. This means that you can only move as many
mailboxes as log space allows in between regular backup jobs.
Like what you're reading? Get the latest updates and tech guides in
your inbox.
G E T E X C L U S I V E U P D AT E S
We can keep track of the migrations using the Exchange Management Shell
by calling the Get-MoveRequest cmdlet, again specifying the BatchName;
then piping the output to Get-MoveRequestStatistics to gain a detailed insight
into our current batch of migrations:
Get-MoveRequest -BatchName "<Database>" | Get-MoveRequestStatistics
18 COMMENTS SHARE
If you’d prefer to use the Exchange Admin Center rather than PowerShell to
co-ordinate the migration, then consider using the migration batches, as
shown during our test mailbox moves.
Figure 3: Using the EAC interface to the New Migration Batch cmdlets
Use the New Migration Batch wizard to select mailboxes from the Global
Address List, as shown below:
18 COMMENTS SHARE
After creating and starting a migration batch via the Exchange Admin Center,
we can examine the progress of those moves by selecting the migration batch
from the list, and then choosing View Details:
We’ll then be presented with a list of all mailboxes within the batch, each of
which can be selected and the full status available for detailed examination:
18 COMMENTS SHARE
Either of these two methods is equally effective, and whichever you use is
down to which ever method makes most sense within your organization.
After performing migrations of end users you can verify that no additional
mailboxes remain on Exchange 2010, using the following command at
the Exchange 2016 Management Shell:
Get-Mailbox -Server <Server>
If any mailboxes do remain, then pipe the results of the command to the New-
MoveRequest cmdlet as a new migration batch, for example:
Get-Mailbox -Server <Server> | New-MoveRequest -BatchName "Remaining Mailboxes"
We’ll also need to move the system mailboxes from Exchange 2010. We’ll
find these by using the Get-Mailbox cmdlet with the –Arbitration parameter:
Get-Mailbox -Server <Server> -Arbitration
You’ll expect to see a couple. Move them to Exchange 2016 using the New-
MoveRequest cmdlet again:
Get-Mailbox -Server <Server> -Arbitration | New-MoveRequest
After all mailbox moves from the Exchange 2010 server are complete,
remove the mailbox move requests from Exchange 2016.
To remove successfully completed move requests, use the Remove- 18 COMMENTS SHARE
If you opted to use the Migration Batch method then you can remove it via
the Exchange Admin Center by viewing the batch, and then if it is complete,
hitting the Delete button:
Before removing the staging server, it’s important to verify that these servers
are definitely no longer used. For example, if you have devices
that use the Exchange 2010 server for SMTP relay, double check that all
these devices have been updated to use the Exchange 2016 server.
Also double check you’ve implemented and migrated mail flow. We’ll need 18 COMMENTS SHARE
to verify that both Inbound and Outbound mail (via Receive and Send
Connectors respectively) is configured to flow via Exchange 2016 only.
SECTIONS TECH NEWS TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT
After checking that mail flow should no longer be configured to flow through
the Exchange 2010 infrastructure, we should be ready to remove Exchange
2010 completely. To ensure that this is definitely the case, shut down
the Exchange 2010 server and leave switched off for a reasonable period of
time (for example, a week) to ensure that should anything have been missed
the Exchange 2010 server can be started up and anything that wasn’t
originally identified migrated.
We'll remove the old Exchange 2010 one by opening the Exchange
Management Console and navigating to Organization
Configuration>Mailbox and then within the Offline Address Book tab
selecting the original address book, with the Generation Server specified as
the old Exchange 2010 server. Simply choose Remove:
Removing Databases
Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 6)
http://techgenix.com/migrating-small-organization-exchange-2010-exchange-2016-part6/ 8/17
2/5/2018 Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 6) - TechGenix
In our example organization we do not use Public Folders, therefore we only 18 COMMENTS SHARE
have one type of Database we need to remove from our Exchange 2010 -
Mailbox Databases.
SECTIONS TECH NEWS TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT
Before we press ahead and remove the databases, we'll need to double check
that all mailboxes have been moved to Exchange 2016.
To verify all mailboxes have been removed from our Exchange 2010 server,
we'll use the following commands:
Get-Mailbox -Server <ServerName>
Get-Mailbox -Server <ServerName> -Arbitration
Get-Mailbox -Server <ServerName> -Archive
After verifying that no mailboxes exist on the server, we're ready to remove
the databases. As part of this process Exchange 2010 will double check that
no mailboxes exist. It will not allow the removal of databases that contain
mailboxes.
We’ll use the following PowerShell command from our Exchange 2010
server to first get a list of the databases:
Get-MailboxDatabase –Server <ServerName>
After confirming that the command is showing the correct databases, remove
the Mailbox Databases using the following command;
Get-MailboxDatabase –Server <ServerName> | Remove-MailboxDatabase
To do this, navigate to Programs and Features, within the Control Panel and
choose Uninstall after selecting Microsoft Exchange Server 2010 from the list
of installed applications:
18 COMMENTS SHARE
The Exchange Setup application is used for the uninstallation process, much
like it was used for the original installation. When prompted, we'll
therefore unselect each Exchange Role installed, for example Client Access,
Hub Transport and Mailbox.
After choosing Next, Exchange Server Setup will perform checks to ensure
that we're actually ready to uninstall. After moving Send Connectors earlier
in this series and performing the tasks in this article, we'll expect each
readiness test to complete successfully, allowing us to choose Uninstall:
18 COMMENTS SHARE
After choosing Uninstall we'll expect the setup program to continue with
removal of Exchange 2010. After it completes successfully the server can be
decommissioned, and the server removed from the domain.
Summary
In this six-part series we’ve walked through a straightforward migration to
Exchange 2016 from Exchange 2010. If you had experienced migrations
between previous versions you will have seen that in comparison, the
Exchange 2016 migration process is relatively straightforward.
If you would like to read the other parts in this article series please go to:
Featured Links
READ Migrating
NEXT a small organization from Exchange 2010 to Exchange 2016 (Part 6)
http://techgenix.com/migrating-small-organization-exchange-2010-exchange-2016-part6/ 11/17
2/5/2018 Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 6) - TechGenix
18 COMMENTS SHARE
AUTHOR
Steve Goodman
18 COMMENTS
great article
Hiya,
Steve
Hello,
Steve
“EnableHttp2Tls”=dword:00000000
Hey Dave,
Steve
helpful. After the user receives the message to close and 18 COMMENTS SHARE
SECTIONS
willTECH
fix this fast. Other
NEWS
than these two
TUTORIALS
points, I am
REVIEWS
able to
NEWSLETTERS VIDEOS ABOUT
Well done
Regards
Mark
Your email address will not be published. Required fields are marked
*
18 COMMENTS SHARE
Name* Email* Website
POST COMMENT
SECTIONS TECH NEWS TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT
6 can’t-miss tips
to improve
Windows 10 performance
Skygofree
malware poses
TechGenix reaches millions of IT
serious danger to Android
Professionals every month, and has
users
set the standard for providing free
technical content through its Self-aware robots
growing family of websites, — science- ction
empowering them with the answers or reality?
and tools that are needed to set up,
configure, maintain and enhance
their networks.
Copyright © 2018 TechGenix Ltd. | Privacy Policy | Terms & Conditions | Advertise
http://techgenix.com/migrating-small-organization-exchange-2010-exchange-2016-part6/ 17/17