Hi, I am working on a new Exchange 2010 migration. Customer have 3 domains, Domain 1 - Exchange 2010 Domain 2 - Exchange 2007 and 2003 Domain 3 - Exchange 2007 All users are moving to Domain 1. I am using FIM Galsync to sync all the users, which is working good, I get "Cross-forest mail contacts" in Domain 1 and Contacts in Domain 2 and 3. When I run the Prepare-moverequest.ps1 the mailbox is getting converted to a mailenable user, which is correct. But then when the next Galsync Run profile is being executed. the contact is being synced over again. And I then end up with 2 users, one is Mail user, the other is Cross-forest mail contact. Which means duplicate contacts in the GAL. Anyone had the same problem? should I modify the GALSync filters? I could move the user to the OU that FIM is pulling users from in Domain 1, when I run the prepare-moverequest. And then move the OU out from the OU where FIM is pulling users from in Domain 1 or Domain 2. Because the users from Domain 1 would be synced over as a contact to Domain 2 and 3. But I would prefer not todo that, as this would add more steps in the migration. As this is a large environment.viklund

Viklund, You will need to add a step to the powershell script to hide the old mailbox from the GAL or to set some other attribute which you then use to filter it out as you import from domain 2 or 3.David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

Hi David, Thanks for you reply, But I solve this with assistant from Microsoft Premium support. We rewrote the .dll file. viklund