Migrating A Small Organization From Exchange 2010 To Exchange 2016 (Part 6)

2/5/2018 Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 6) - TechGenix
 18 COMMENTS  SHARE
SECTIONS  TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT  
Migrating a small organization FEATURED PRODUCT
from Exchange 2010 to

Exchange 2016 (Part 6)
Steve Goodman 1  8 Views  18
POSTED ON MARCH 28, 2016
 SHARE ON FACEBOOK  TWEET IT   

Get expert tech
reports and guides
for FREE!
Join 900,000 fellow IT Pros...
and be among the rst to learn

about new security threats, system
optimization tricks, and the hottest
technologies in the industry.
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

(Part 1)
Cookie policy
(Part 2)
(Part 3)
FEATURED FREEWARE
(Part 4)
Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 6)

http://techgenix.com/migrating-small-organization-exchange-2010-exchange-2016-part6/ 1/17
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
and moving test mailboxes didn’t expose. Permissions

Analyzer!
First we will select a pilot group of users to migrate to Exchange Server

2016. They should provide feedback on any issues they encounter, and will
represent a cross-section of end-users; for example users that are heavy
mobile users, those that are primarily external users and those that regularly RECOMMENDED
use features like shared calendars and delegation.
Deploying
RECOMMENDED Exchange
Server 2016
Exchange 2016 upgrade tips and tricks from the (Part 1)
eld (Part 3)
Planning and
migrating a
small
Many smaller organizations will find most pilot candidates within the IT organization
department, but if you have users who are keen to be early adopters outside from
Exchange 2007
of IT, then you’ll get a better representation of real issues. to 2013 (Part 9)
Under the
hood:
Migrating Mailboxes Microsoft
Exchange 2016
When migrating mailboxes from Exchange 2010 to Exchange 2016, we’ve deployment
architecture
got a number of methods that can be used to migrate mailboxes in large
numbers.
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

Figure 1: Creating new move requests
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.
You can mitigate against this by either performing additional incremental

backups during mailbox migrations; or temporarily turning on circular
logging.
Like what you're reading? Get the latest updates and tech guides in
your inbox.
Enter your email address...
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

Figure 2: Monitoring move requests from PowerShell
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:

Figure 4: Adding mailboxes to the new migration batch
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:
Figure 5: Viewing the list of Migration Batches
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:

Figure 6: Monitoring progress of a Migration Batch
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
MoveRequest cmdlet in combination with the output of Get-MoveRequest:
SECTIONS  TECH NEWS  TUTORIALS REVIEWS

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest NEWSLETTERS VIDEOS ABOUT  
Figure 7: Removing completed move requests
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:
Figure 8: Removing a completed batch
Decommissioning Exchange 2010
Getting ready to decommission

Exchange 2010
By this point, we should be safe to remove Exchange 2010 from the
environment. Earlier in the series we moved inbound and outbound mail flow
to Exchange 2016, moved client access across; and we have just completed
migrating all Mailboxes over to Exchange 2016.
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.
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.
Removing unused Of ine Address

Books
We'll start off with a relatively simple task, removing the old default Offline
Address Book.
As part of the installation of Exchange 2016, a new Offline Address Book

was created and set as the default. This will have the
suffix (Ex2013) signifying it is created by Exchange 2013 or above.
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:
Figure 9: Removing obsolete Offline Address Books
Removing Databases
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.
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
Uninstalling Exchange 2010

With Mailbox Database configuration removed we can now uninstall
Exchange Server 2010.
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:

Figure 10: Uninstalling Exchange 2010
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.
Additionally, we'll choose to uninstall the Management Tools - which

includes the Exchange Management Console and Exchange Management
Shell:
Figure 11: Uninstalling all components of Exchange 2010
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:

Figure 12: Verification of successful uninstallation
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:

(Part 1)
(Part 2)
(Part 3)
(Part 4)
(Part 5)
Featured Links
READ Migrating
NEXT a small organization from Exchange 2010 to Exchange 2016 (Part 6)
How to migrate Load balancing Exchange 2016

from Microsoft Exchange Server upgrade tips and
Exchange 2010 to 2016 (Part 1) tricks from the
Exchange 2016 eld (Part 2)
Load balancing Migrating Public Migrating a small

Exchange Server Folders to organization from
2016 (Part 2) Exchange 2013 Exchange 2010 to
(Part 1) Exchange 2013
(Part 1)
TECHGENIX » MS EXCHANGE SERVER » DEPLOYMENT & MIGRATION » MIGRATING A SMALL

ORGANIZATION FROM EXCHANGE 2010 TO EXCHANGE 2016 (PART 6)
AUTHOR
Steve Goodman
Steve is a 5 times recipient of the MVP (Microsoft’s Most

Valuable Professional) award from Microsoft, is a
regular international conference speaker, podcast host,
regular blogger, plus he is the author of a number of
popular Exchange books. Steve is Head of Messaging
and UC at top Of ce 365 partner Content and Code,
responsible for their Exchange and Skype for Business
offerings. Steve has worked on a vast number of
Exchange and Of ce 365 projects across customers
large and small, often with complex requirements and
loves to share his expertise.
18 COMMENTS
Siegfried May 9, 2017 at 5:34 am R E P L Y
Very much thanks for this article!

eran May 30, 2017 at 4:24 am R E P L Y

great article
you sould add a part about migrating public folders. 

SECTIONS  TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT 
Steve Goodman January 5, 2018 at 4:59 am R E P L Y
Hiya,
We have other public folder migration articles on the site

that can be used in combination – As this was already a
multi-part series, I didn’t want to make things too
repetitive.
Steve
El May 31, 2017 at 8:58 am R E P L Y
Can you expand on user experience while their mailbox is

being migrated. Thank You
Hello,
During migration a user shouldn’t see any noticeable

effects as the migration can be performed online. Once
the migration completes, they will be prompted to re-sta
Outlook. However, there is a small amount of time that
the client will be disconnected straight after the move
completes, so I recommend completing moves out of
hours.
Steve
Will June 1, 2017 at 11:23 am R E P L Y
Best step-by-step for an Exchange migration I have found

yet. Just completed a 2010 to 2016 migration following this
process and it could not have gone smoother. Thanks for
taking the time to write such a great article.

Greg June 22, 2017 at 5:30 pm R E P L Y

Will, is there any downtime during any of these steps or

do both 2010 and 2016 operate at the same time with no
SECTIONS  TECHdown
NEWStime
 byTUTORIALS
both talking REVIEWS
to each other? Can someone
NEWSLETTERS VIDEOS ABOUT  
log into OWA on 2016 and access their email if it still

resides on 2010? Thanks!
Thomas July 3, 2017 at 4:49 pm
Greg, the only downtime is whey the mailbox is in

transit to the new server.
Example, after you queue a group of mailboxes to

migrate, they begin to transfer 1 at a time. During the
actual transfer and only then, that mailbox will be
unavailable – Outlook shows disconnected. When the
mailbox has completely moved, the Outlook client is
automatically updated to point to the new server and
you’re back online.
GhostyDog August 1, 2017 at 4:54 am R E P L Y
Great article, really helped me when migrating from SBS

2011 to Exchange 2016, still valid even now, although there
have been a few changes since it was written.
Miroslav September 14, 2017 at 5:17 am R E P L Y
Hello, I have followed this guide step-by-step, but when

Iam trying to move/migrate first mailbox, this mailbox is
still in synchronization Status. Mailbox isnt moved to new
2016 server. Still synchronizing. Where could be the
problem ? Thanks
Hiya, sorry for the late reply. I would suggest examining

the detail of the move request, which should show you
the move request log. This should show some indication
on whether it is simply migrating, or there is some issue
(such as a connectivity issue).

Johan Ljunggren November 4, 2017 at 5:06 am R E P L Y

Thanks for an awesome article – looking forward to the

next one for migrating 2016 to 2019 🙂
Only problem I had was with IOS and macOS devices that
did not support http/2 which IIS in Windows Server 2016
defaults to. But after disabling that (a lot of articles out the
on how to do that in the registry) those worked as well.
“EnableHttp2Tls”=dword:00000000
Paul December 21, 2017 at 7:29 am R E P L Y
Thank you Steve! This was spot on and it took a lot of

guessing out of the whole process.
Dave January 4, 2018 at 4:50 pm R E P L Y
I have just today moved by test group. For some reason

when i tested switching my old 2010 exchange server off
none of these mailboxes work or the ECP is not accessible.
Any ideas whats gone wrong? Seems my 2016 exchange
will only work when 2010 server is on and running.
Hey Dave,
Where are the DNS records for your Exchange servers

pointing at? Are they pointed at the 2010 servers still, or
only at the Exchange 2016 servers?
Steve
Ken January 10, 2018 at 2:38 pm R E P L Y
This article has helped me more with 2010 to 2016

migrations than any other. I would install Exchange 2016
after hours, so that there is enough time to set the SCP,
install a valid certificate in 2016, and change
internal/external URLs. The chance of invalid cert pop-ups
in Outlook is too great. I also move most mailboxes after
hours, but if performed during hours I found a tip that is
helpful. After the user receives the message to close and  18 COMMENTS  SHARE
restart Outlook, Outlook will show as disconnected.

Restarting the AutoDiscover app pool on the 2016 server
SECTIONS 
willTECH
fix this fast. Other
NEWS 
than these two
TUTORIALS
points, I am
REVIEWS
able to
NEWSLETTERS VIDEOS ABOUT  
do everything else during business hours. I have found

Public Folders to be a pain and that migration should be
done after hours. Today I ran into an issue in which I had to
go through the Public Folder migration procedure, even
though there were no Public Folders in the old database. I
couldn’t remove the old Public Folder database until I went
through the migration steps.
Mark Jones January 11, 2018 at 2:44 am R E P L Y
Excellent guide for migrating to E2K16. Have already read

the ms exchange deployment assistant, reading this guide as
well give a great amount of configuration assistants.
Well done
Mark Jones January 11, 2018 at 2:49 am R E P L Y
One problem I keep seeing after a mailbox is moved to exch

2013 or 2016 is the client in a disconnected state or
prompting for a password for several hours… first thing to
do at this point is recycle the Autodiscover web apps pool in
is on the server you moved the mailbox to. Its a know issue
with caching Autodiscover connections
Regards
Mark
Your email address will not be published. Required fields are marked
*

Name* Email* Website
POST COMMENT
NOTIFY ME OF FOLLOW-UP COMMENTS BY EMAIL .
NOTIFY ME OF NEW POSTS BY EMAIL.
TECHGENIX RECENT POSTS
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  

Migrating A Small Organization From Exchange 2010 To Exchange 2016 (Part 6) - TechGenix PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Migrating A Small Organization From Exchange 2010 To Exchange 2016 (Part 6) - TechGenix PDF

Enviado por

Direitos autorais:

Formatos disponíveis

2/5/2018 Migrating a small organization from Exchange 2010 to Exchange 2016 (Part 6) - TechGenix

SECTIONS  TECH NEWS  TUTORIALS REVIEWS NEWSLETTERS VIDEOS ABOUT  

Migrating a small organization FEATURED PRODUCT

from Exchange 2010 to

POSTED ON MARCH 28, 2016

 SHARE ON FACEBOOK  TWEET IT   

Join 900,000 fellow IT Pros...

and be among the rst to learn