Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 724
  • Last Modified:

Office 365 Staged Migration

Im about to do an Staged Migration from an Exchange 2007 to Office 365.

Im following this from Microsofts TechNet:  http://technet.microsoft.com/en-us/library/jj874018(v=exchg.150).aspx

But in Best Practice in the bottum of page it says:
Inform users before you start the batch, because they'll stop receiving email sent to their on-premises mailboxes soon after the TargetAddress property is configured to forward mail to their Exchange Online mailbox.

Why does the On-Premises server stop receiving mail then i havent moved the MX record?

I trought I could create all the users and then sync all the email, test if it works on Office 365, move the MX and then make a final sync.
0
KortermannIT
Asked:
KortermannIT
  • 3
  • 3
2 Solutions
 
XaelianCommented:
Hello, your on-premise server doesn't stop receiving the mail. It just forwards it to the Exchange Online server. This only happens when the synchronisation of the mailboxes has finished.

Best you can do is perform a dirsync and then launch the staged migration. If you perform the sync of all the users it does everything. MS has done this to make sure that you don't need to resync everything once again when everything has finished.

Depending on the size of the environment I would advise you to start this migration friday night, so you can do the configuring of the desktops saturday.
0
 
KortermannITAuthor Commented:
Then the on-premise server forwards all the email to Exchange Online Server, does it make a copy or is it moving the mail?

Right now I have made an DirSync and was about to make a staged migration, until i read that then the sync is done, the on premise would be deactivated and only Office 365 would work.

As I said in my first post, I tought I could test public folders, shared folders, mailbox etc. before i reconfigured all the clients.
0
 
XaelianCommented:
It doesn't make a copy on your on-premise mailbox.
When Office 365 had Exchange 2010 it was possible, but after the Exchange 2013 it wasn't.
0
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

 
KortermannITAuthor Commented:
Okay, thanks! :)
0
 
XaelianCommented:
Also a quick tip: don't trust the GUI. Especially for the mailbox delegation. If you select 5+ users to have Full Access it won't place all those users into the mailbox delegation settings. Powershell is your friend.
0
 
KortermannITAuthor Commented:
For this?
The following list shows the administrative privileges required to migrate mailboxes using a staged migration. There are three possible options.
¿ The migration administrator must be a member of the Domain Admins group in Active Directory in the on-premises organization.
 Or

¿ The migration administrator must be assigned the FullAccess permission for each on-premises mailbox AND the WriteProperty permission to modify the TargetAddress property on the on-premises user account.

But the GUI have allready screwed me. It wont accept my CSV, and the log says absolute nothing, I can use. So now I will try PowerShell (Without the auto-start feature).
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now