Exchange 2010 Cross-Forest Mailbox Move and AD Migration
Hello,
I am in the middle of an Active Directory migration, during the last phase I will be migrating the user accounts and mailboxes, all at the same time, over a long weekend.
My plan is to run the Prepare Move Request script in exchange 2010, then migrate the accounts with the ADMT tool and then move the mailboxes.
At a some point during that weekend I will need to forward incoming emails to the new server versus the old.
My question is just at what point? Do I need to wait until all mailboxes have finished moving?
I am planning on "SuspendWhenReadytoComplet
Also any tips you can provide to deal with active sync and anything else you can thin of will be welcome.
Thanks,
I am in the middle of an Active Directory migration, during the last phase I will be migrating the user accounts and mailboxes, all at the same time, over a long weekend.
My plan is to run the Prepare Move Request script in exchange 2010, then migrate the accounts with the ADMT tool and then move the mailboxes.
At a some point during that weekend I will need to forward incoming emails to the new server versus the old.
My question is just at what point? Do I need to wait until all mailboxes have finished moving?
I am planning on "SuspendWhenReadytoComplet
Also any tips you can provide to deal with active sync and anything else you can thin of will be welcome.
Thanks,
Marc Dekeyser
it is obvious that you prepared this well enough, but have you read this article? http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
Mail boxes don't move.
The New AD Domain creates new blank mailboxes for the users. The users needs to be using them first (with the mail going to the new mail server). Then use whatever chosen means you are using to copy (not move) the contents of the old mail boxes into the new mail boxes. The users will simply have to survive for a short period of time without their old messages. If you are doing it over the week end then you may be able to complete the whole thing before the users get involved.
Users and not move either
The migration process never moves anything,...it copies. It simply makes new user accounts in the new Domain that are spelled the same and may have the same password. The new accounts get a new SID,...so they are not really the same old account. However the ADMT process can add the old SID to the account as a secondary SID in oder for the Account to impersonate the old account. But it is still a distinct new account,...that only impersonates the old account via the SID history
The New AD Domain creates new blank mailboxes for the users. The users needs to be using them first (with the mail going to the new mail server). Then use whatever chosen means you are using to copy (not move) the contents of the old mail boxes into the new mail boxes. The users will simply have to survive for a short period of time without their old messages. If you are doing it over the week end then you may be able to complete the whole thing before the users get involved.
Users and not move either
The migration process never moves anything,...it copies. It simply makes new user accounts in the new Domain that are spelled the same and may have the same password. The new accounts get a new SID,...so they are not really the same old account. However the ADMT process can add the old SID to the account as a secondary SID in oder for the Account to impersonate the old account. But it is still a distinct new account,...that only impersonates the old account via the SID history
ASKER
Thanks Geminon, I have read that article several times. :-)
So, pwindell, if I understand you correctly, the prepare move request will create the account and mailbox, then the ADMT tool will just basically "stamp" the old SID in the SID history attribute and get the group membership, etc done. So then I should switch the email to flow to the new server anytime after I run the prepare move request script? Is that correct?
Thanks a lot, I think I got it, I just really want to confirm my ideas.
So, pwindell, if I understand you correctly, the prepare move request will create the account and mailbox, then the ADMT tool will just basically "stamp" the old SID in the SID history attribute and get the group membership, etc done. So then I should switch the email to flow to the new server anytime after I run the prepare move request script? Is that correct?
Thanks a lot, I think I got it, I just really want to confirm my ideas.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Lastly,...do not wipe out the old domain and the old Exchange for a period of time. That will be how you preserve the old email and you may have to go back and grab stuff if the process get screwed up the first time around.
The migration is non-destructive to the old domain,...even the old machine accounts are left behind. The old user accounts may or may not be disabled during the process (depends on the option you choose in ADMT). But in any case leave the old Exchange and old DC fully intact for a period of time after.
The migration is non-destructive to the old domain,...even the old machine accounts are left behind. The old user accounts may or may not be disabled during the process (depends on the option you choose in ADMT). But in any case leave the old Exchange and old DC fully intact for a period of time after.
ASKER
Thanks, I have read all that I can find out there about this, and the ADMT guide, several times.
I have already done a test run in a lab as well and my live environment is ready to go as well.
I am just ironing out the last details.
Thanks for all your input, I appreciate it.
I have already done a test run in a lab as well and my live environment is ready to go as well.
I am just ironing out the last details.
Thanks for all your input, I appreciate it.