Staged Migration

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
2 hours 42 minutes
Difficulty
Beginner
CEU/CPE
3
Video Transcription
00:00
>> Hello and welcome back to
00:00
the Office 365 migration primer course.
00:00
I'm your instructor, Jim Daniels and
00:00
today we're going to study on Module 4;
00:00
Exchange Online and we're
00:00
going to go over staged migrations.
00:00
In this lesson, we're going to talk
00:00
about what a staged migration
00:00
is and what situation is recommended.
00:00
To use a staged migration,
00:00
you need to have on-premise Exchange 2003 or 2007.
00:00
It's recommended for over 2,000
00:00
mailboxes and you move
00:00
mailboxes in small batches over time.
00:00
Some notes about setting up a staged migration.
00:00
First, the users all need to be synced to Office
00:00
365 via Azure Active Directory Connect.
00:00
Your on-prem users that
00:00
their mailboxes are going to go to Exchange Online,
00:00
they all need to have
00:00
their user objects populated in Azure AD.
00:00
You need to configure Outlook Anywhere,
00:00
RPC over HTTP for your on-prem.
00:00
Outlook Anywhere is required
00:00
for a staged migration to work.
00:00
Your certificate on your Outlook Anywhere
00:00
has to be from a trusted CA.
00:00
It can be a locally signed cert.
00:00
You create a CSV file for your mailboxes to migrate,
00:00
up to 2,000 rows per CSV.
00:00
Finally, once the mailboxes are
00:00
converted and they're migrated in the Cloud,
00:00
they need to have their on-premise designation change
00:00
to mail-enabled user.
00:00
That will allow them to receive mail on Exchange Online.
00:00
After that, you want to create
00:00
your auto-discover DNS record and update your MX record.
00:00
Let's look at the flow of a staged migration.
00:00
This diagram is direct from Microsoft.
00:00
Again, at the very beginning,
00:00
you have to have your user objects in Azure AD,
00:00
you're on the sync.
00:00
Users are created.
00:00
You create the CSV file.
00:00
You run the staged migration batch.
00:00
You get the report, everything is good.
00:00
You go ahead and convert
00:00
those mailboxes on-prem to mai- enabled user.
00:00
You have to do that or otherwise they will not
00:00
receive mail in Exchange Online during the migration.
00:00
After that, they can actually receive mail.
00:00
You run and repeat.
00:00
Another CSV file.
00:00
You import a batch,
00:00
configure those users, the mail-enabled user.
00:00
Once you finish up,
00:00
all of the users are in
00:00
the Cloud and all of them can receive from their mailbox.
00:00
Then you can go in and delete
00:00
the migration batches and
00:00
you can start on the post-migration task.
00:00
That includes even decommissioning
00:00
your on-prem exchange if you want to go that route.
00:00
It also includes updating
00:00
your MX and the auto-discover records in
00:00
your public DNS to have those
00:00
facing Office 365. Quiz time.
00:00
Staged migration is an option for an organization with
00:00
2,350 mailboxes
00:00
in an Exchange 2010 on-premises environment.
00:00
You have two factors here,
00:00
2,350 mailboxes that need to be
00:00
migrated in Exchange 2010 on premise.
00:00
Is staged migration a candidate for this scenario?
00:00
The answer is false.
00:00
The 2,350 that number checks out.
00:00
You can totally use staged migration for that.
00:00
However, Exchange 2010
00:00
is not compatible with a staged migration,
00:00
it has to be Exchange 2003 or 2007.
00:00
To recap this module, staged migration, again,
00:00
only available on-premise Exchange 2003 and 2007.
00:00
A CSV file is required for migration and
00:00
you can migrate 2,000 plus mailboxes overtime.
00:00
Thank you for taking time out of
00:00
your schedule to join me.
00:00
I hope to see you next time. Thank you.
Up Next