Due to mergers and acquisitions, I am in a scenario where I need to migrate two Exchange Orgs in separate forests to my Org / forest. Also, I am in the middle of an Exchange 2007 to Exchange 2013 migration myself... fun times.
Anyway, for purposes of my post, consider this scenario:
DomainA - my domain. Exchange 2007 SP3 and Exchange 2013 SP1 in coexistance mode, AD 2003 native mode. In the middle of an internal migration of all mailboxes from 2007 to 2013.
DomainB - one of the "acquired" domains. Exchange 2010 SP3 UR5, AD 2003 native mode
DomainC - one of the "acquired" domains. Exchange 2007 SP3 UR13, AD 2003 native mode
I need to "merge, move, migrate" all AD objects and mailboxes from DomainB and DomainC to DomainA.
1. Verify full network connectivity and DNS resolution between DomainB and DomainA and between Domain C and DomainA
2. Establish two-way transitive trusts between DomainB and DomainA - DONE
3. Establish two-way transitive trusts between DomainC and DomainA - DONE
4. Verify all trusts are working, both ways. Test adding rights to resources in both domains - DONE
5. Disable SID filtering on all domains via GPO, set the forest trusts to disable sid filtering via netdom - DONE
6. Set up ADMT Server with SQLExpress and ADMT 3.2 on one server in DomainB and DomainC - DONE
7. Set up "Passwerd sync DLL Tool" on a DC in DomainB and DomainC - DONE
8. Verify ADMT is working correctly by migrating an account from DomainB to DomainA including SID history and Group Membership and password sync - DONE
9. Verify ADMT is working correctly by migrating an account from DomainC to DomainA including SID history and Group Membership and password sync - DONE
So by this point, I think I am pretty slick and things are working great, right? Not so much. I attempt to do test Exchange mailbox migrations and things go to hell. Especially from the 2007 side of things.
I find out that the ADMT, apparently by design does not migrate certain mandatory AD attributes which are required by Exchange. I then find out that there is a powershell script Prepare-MoveRequest.ps1 which can fix some of these things. I take a look at it and I am "deer in headlights" mode. I consider myself pretty decent at powershell, but I cannot comprehend some of the things going on in this script. Plus it does not work on Exchange 2007.
So I take a step back and think hard about this. I had originally planned on doing the new-mailboxmoverequest in "pull" mode from Exchange 2013 DomainA. I think what I am going to do instead is this procedure:
10. Export all mailboxes from DomainB to .PST files via powershell (wait... wait...)
11. Migrate all user objects, group objects, contacts, etc from DomainB to DomainA via ADMT
12. Create new "dial-tone" Exchange 2013 mailboxes in DomainA for each migrated user account from DomainB
13. Add DomainB as an accepted domain in DomainA's Exchange Org
14. Move DomainB's MX record to point to the external MTA for DomainA
15. Add DomainB email domain name as an accepted email address for each migrated user via email address policy
16. Import pst files via powershell for each mailbox created in step 12
17. Wait... wait... wait some more, eventually this will finish
18. Desktop team re-images all DomainB PC's with DomainA image, joins these PC's to DomainA (not my task... but will happen at the same time this is occuring)
19. Users log in to newly imaged PC's using their migrated DomainA credentials and are able to open Outlook successfully and access resources (servers, shares) in DomainA and DomainB. Users able to receive mail from username@domainA and username@DomainB
18. Repeat steps 10-19 for DomainC to DomainA on a different date
I have tested this scenario and it works. But is very time consuming. I might find I have to set up mail enabled users on DomainA and use DomainA as a relay domain in a sort of phased migration approach. I have done this before. It's not a huge number of users we are talking about, a few hundred per domain. I have thousands in my DomainA, so that's why I am still in the middle of migrating from 2007 to 2013, they kind of sprung this on me arbitrarily. It was supposed to happen after we finished our 2007 to 2013 migration.
One question is about Archive Mailboxes in the 2010 DomainB, I assume those can be exported and imported like a normal mailbox? I have not tried this yet.
Thoughts and suggestions?
< Message edited by troy12n -- 21.May2014 12:12:58 PM >