FIM Knowledge Bit Source: OLSync with FIM 2010 experiences As Craig Martin explains: Approach 1: Install OLSync on ILM 2007, then upgrade to FIM 2010 If you already hav OLSync running on ILM then just upgrade to FIM 2010 and you'll probably find that the system just works, because: 1. The FIM setup process will upgrade the ILM database 2. The FIM setup process will take the stored copies of the DLLs from the database and drop them to the new FIM Sync Server 3. FIM Sync can host the DLLs that were previously run by ILM, even tho they were running on x86 and are now running on x64 Steps : Copy the ILM database to the SQL server running on the new box (x64) Install FIM Sync on the new box When FIM Sync Setup prompts you for database details, specify the SQL instance you copied the ILM database to Setup will upgrade the ILM database to FIM Approach 2: Perform the 'Extract Files' Install of OLSync the Import the Server Config in FIM Sync The 'Extract Files' option in the OLSync installation does minimal pre-req checking, and essentially drops the files from the MSI into a folder on your server. You can use the resulting files to deploy OLSync to FIM Sync because those files include: 1. 'Server Exports' which are just XML dumps of a sync server that can be imported into another server. 2. The DLLs you need to put into the 'Extensions' folder on the FIM Sync server 3. The XML files you need to put into the UIShell folder to make FIM understand the 'OLMA' management agent type Related posts: - how to configure ADMA and galsync forfront identity manager 2010 - Provisioning to Live(at)EDU with FIM 2010 RC1. (How to configure the MA) - Live(at)edu OLSync on FIM 2010 (Dmitry Kazantsev) Go to the FIM Knowledge Bit Collection Peter Geelen - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]