Cutover Migration Batch complete - Next steps to get to DirSync

Migrating to Office 365 in a cutover migration.
Migration batch is complete.
All users are licensed (odd requirement that had to occur)

Question:
What is the next step? Delete Migration Batch?

Do I schedule downtime with users at this point?
Do I point MX records (to 365) after I delete the Migration Batch?
Do I then run DirSync during this outage window?
LVL 8
K BAsked:
Who is Participating?
 
Vasil Michev (MVP)Commented:
Dirsync can wait, make sure everything is migrated properly, then complete the batch and switch the MX. In the meantime, you can run some checks to make sure the cloud users will be correctly matched with the on-prem ones. As the cutover process uses the WindowsEmailAddress to provision accounts, make sure all the relevant attributes are properly configured and there will be no surprises later.

Since the objects are already created, you might end up with duplicate objects in dirsync fails to 'match' them. The usual process is to just get rid of the new one (the one that does not correspond to a mailbox) and redo the sync, this time making sure that the primary SMTP addresses match. Here's the article describing the soft-match process: http://support.microsoft.com/kb/2641663
0
 
K BAuthor Commented:
1. Change MX
2. Disable on-premise AutoDiscover and ActiveSync
3. Install & configure DirSync
4. Create autodiscover record
5. create new profile for all user's Outlook and mobile device
6. Delete the cutover migration batch.
0
 
K BAuthor Commented:
downtime should be scheduled over an evening.
0
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
K BAuthor Commented:
With on-premise Exchange 2007, prior to DirSync, you have to convert all the Exchange users to Mail-Enabled Users (MEUs) in AD.
0
 
Vasil Michev (MVP)Commented:
Not necessarily, it's recommended but not mandatory. You can soft-match against mailboxes too.

The only issue you might run into is for mailboxes that weren't copied during the cutover process (i.e. hidden from the GAL or failed for some reason). As you have active on-prem mailbox for those objects, the relevant attributes will be synced to EO. You will not be able to create mailbox in EO for such objects unless you convert the on-prem mailbox to MEU.
0
 
K BAuthor Commented:
Confirmed what you said that it is not necessary to convert to MEUs .... Yet again, Vasil, many thanks!!!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.