I am somewhat confused as to how I should combine different migration tools and techniques. We have three Win2003 user forests (A-B-C), each with Exchange 200x servers in them, and all mailboxes need to be migrated to a fourth resource forest (D).
What I've done so far:
- created the forest D, installed Ex2007 SP1
- created bidirectional forest trusts between A-B-C and D
- installed and configured IIFP; this creates a contact in D for every user in A-B-C
- migrated some pilot users to D to test migration scripts and SMTP routing (this uses Move-Mailbox and deletes the contact)
What currently happens is this:
- IIFP creates the contact
- Move-Mailbox creates a mailbox-enabled disabled user, based on that contact. The mailbox is migrated.
- Move-Mailbox takes over all existing SMTP addresses of the original user
- Move-Maibox deletes the original user mailbox, and the user becomes mail-enabled instead of mailbox-enabled, pointing to the new Ex2007 organization
- Move-Mailbox changes CustomAttribute2 to trigger Address Policies on the new server
- Move-Mailbox deletes the contact
This all seems to work perfectly.
Now the next task is to migrate all distribution groups to D. Apparently I should use ADMT, but I cannot find the correct order in which to do things. If I migrate a user with ADMT, it creates a disabled user in D without e-mail addresses. The group is migrated as well, but only with that user in it, and no e-mail address. Ex2007 doesn't recognise it as a Distribution Group, even if I manually add an e-mail address.
The ideal situation would be that distribution lists can be migrated and contain contacts (created by IIFP) at first, which are then replaced by the disabled users with migrated mailboxes.
How do I combine IIFP, ADMT and Move-Mailbox so that distribution group membership is maintained at all times?
Thanks,
Peter
Start Free Trial
