Hi there, I'm involved on a project that will migrate all resources, accounts and groups from Active Directory (AD) Forest A to a new one called Forest B, that already exists. Well it's expected that all accounts must be migrated from Forest A---> Forest B and kept in sync (including GAL) until the migration is over. Forest A has AD 2003 with Exchange 2003 and Forest B has AD 2008 with Exchange 2007. Questions: 1- Can FIM 2010 migrate and keep accounts and GAL in sync or must I use ADMT 3.1 to migrate accounts and use FIM 2010 do sync accounts and GAL? 2- Is FIM 2010 a big gun to my problem (just keep accounts and GAL in sync)? 3- Can FIM 2010 be thought as a evolution from MIIS 2003, doing the same job as MIIS 2003 and much more? 4- Is MIIS 2003 a better tool to do the job? Is it still supported by MS? 5- Do you know the licensing model for FIM 2010? Thanks in advance and best regards, Eduardo.

1. GALsync = no problem. The big issues to consider with account migration are sidHistory and password. ADMT can copy the old objectSid into the new accounts's sidHistory, allowing the new account to access resources in the old domain without the need for group changes. ADMT can also migrate the existing password. It may be possible to copy the source objectSid into the target sidHistory with FIM (you will still have to enable sid filtering on the domain trust, just as you do with ADMT) however you can't replicate the existing password. 2. It depends how many objects you have, and how regularly the changes will occur. Setting up regular sync tasks can help simplify a complex migration project. 3. The FIM Sync Service is basically a 64 bit version of MIIS 2003. 4. I believe MIIS 2003 is still supported. There is no reason to use it - use FIM 2010 Sync. 5. You can run the evaluation for 180 days. Thereafter you pay a server license for the FIM Sync Service (I think around US 15K). If you want to use the FIM Portal (which has all sorts of other stuff around management, workflow, group population and password reset) you have to pay CALs per managed user. http://www.wapshere.com/missmiis

If all you are looking for is a solution for a migration, you are better off using ADMT. FIM was not designed to handle migrations and can't manage things such as sidHistory, which is in most migration scenarios required. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation