This Guide will explain the detailed steps required to do cross forest migration from source forest running Exchange 2003 to target forest running Exchange 2010.
Active Directory Migration Tool (ADMT) will be used to migrate user accounts as well as computer accounts. There are two scenarios when using ADMT to migrate user accounts with Exchange:
1. Run Prepare-MoveRequest.ps1 script first then ADMT: in this scenario the steps will be in the following order:
a. Prepare-MoveREquest.ps1: The script will be used to create Mail Enabled Users (MEU) in the target forest; the MEUs will be disabled and will contain the following attributes: legacyExchangeDN, mail, mailnickname, msExchmailboxGuid, proxyAddresses, X500, targetAddress, userAccountControl, userprincipalName.
b. ADMT to migrate user accounts: the main target is to get the old SID from the source domain (SID History), and to synchronize the password from the source domain to the new user account in the target domain, of course other AD attributes could be migrated like phone, address, title…
c. Move Mailbox: using new-move request from the source forest to the target forest.
d. ADMT to migrate the computer account: this will mainly disjoin the client machine from the source domain and join the new domain, also will add (or replace) the SID of the new user in the target forest on the same profile used by the old user account, other options available like local group, profiles…..
2. Run ADMT first then Prepare-MoveRequest.ps1: in this scenario the steps will be in the following orders:
a. ADMT to migrate the user accounts from the source forest to the target forest, users will be created or merged by ADMT not the script, SID history and password synchronization along with other AD attributes could be merged from the source forest to the target forest. By default ADMT is excluding all Exchange attributes.
b. Convert the user accounts created or merged by ADMT to Mail Enabled User (MEU) accounts with proxy address as the source forest user account.
c. Prepare-moverequest.ps1: the script will be used with –localobject and –overwritelocalobject switches, so the script will use the existing user accounted and will not create new account.
d. New-MoveRequest: to move the mailbox from the source forest to the target forest.
Choosing which scenario will be based on the customer environment, the selection of the scenario should consider:
This series of articles will focus on the second scenario. Before going on the detailed steps, let’s first explain the environment and the requirements.
The current environment includes the following:
The following diagram shows the details of the current environment:
As the migration will take time, the co-existence period should be considered, so this guide will cover the following:
The second part of this guide will address the migration challenges and setting up the mail flow between the two forests.
Exchange 2010 Cross-Forest Migration Step by Step Guide – Part I
Exchange 2010 Cross-Forest Migration Step by Step Guide – Part II
Exchange 2010 Cross-Forest Migration Step by Step Guide – Part III
Nice - Short N Sweet. i think it would be better to mention about the SID history in a little bit detail as most of the cases we use it to ensure that migrated user is able to use the old domain applications and resources.
Any way I like the Post.
I believe in your first sentence you mean the target is Exchange 2010. Looks like a typo.
Nice introduction. I really like the scenario. Where's Part II? :)
Where is part II?
Thanks all for your comments, Part II and III coming early next week, so stay tuned :).
Great post. Waiting for the next one... :)
I am looking for the part II. Has it posted? If so, URL? Tried googled but no luck.
when the part IV of the article will be released?
Nice one !!
Good One !
Its really nice one!
My situation is a little different from yours. Our customer wants to upgrade from 2007 to 2010 and also change the forest name. Do you recommend upgrading Exchange in source forest or installing ex 2010 in the new forest then migrate?