none
Upgrade MIIS 2003 SP1 to FIM 2010 RRS feed

  • Question

  • We have a environment where we are synchronization user accounts from different data sources like SQL and Oracle. We have MIIS 2003 SP1 and now we are migrating/upgrading to FIM 2010. My query is if we can directly migrate/upgrade to from MIIS 2003 SP1 or do we need to first upgrade it to MIIS 2003 SP2. If we do not upgrade SP2, then what will be the difference?

    Thanks,

    Steve

    Wednesday, September 5, 2012 11:45 AM

Answers

All replies

  • Hi Steve,

    You will need to upgrade to MIIS 2003 SP2 before you can upgrade to FIM 2010.   There is no upgrade path from previous versions of MIIS.

    The following TechNet reference will provide you more insight on the upgrade process:

    FIM REFERENCE: Migrate from MIIS or ILM to FIM 2010

    Cheers,

    Marc


    Marc Mac Donell, VP Identity and Access Solutions, Avaleris Inc.
    http://www.avaleris.com

    Wednesday, September 5, 2012 2:28 PM
  • According to my knowledge, you need to upgrade to MIIS 2003 SP2 first.

    Maybe this url will be of some help to you:
    http://www.wapshere.com/missmiis/upgrading-miisilm-to-fim

    Note: if you want to upgrade to FIM 2010 R2, there are some known issues. It is best to follow this upgrade path:
    MIIS 2003 SP1 > MIIS 2003 SP2 > FIM 2010 (on a new, 64 bit server, with reuse of your current database and assemblies) > FIM 2010 R2

    Here's a link with some considerations for this last upgrade:
    http://technet.microsoft.com/en-us/library/jj134291(v=ws.10).aspx


    Kind regards,
    Pieter de Loos


    Pieter de Loos - Consultant at Traxion (http://www.traxion.com) http://fimfacts.wordpress.com/

    Wednesday, September 5, 2012 2:33 PM
  • Thanks Pieter and Marc for teh response. As of now, we have MIIS 2003 SP1 adn SQL 2000 SP2. so in order to upgrade to FIM 2010 we are export and importing SQL on SQL cluster 2008 and then installing FIM 2010 on new server. After that will point thi FIM installation to SQL 2008 database. Then export and import management agent into FIM 2010.

    Please advise if it is right approach.

    Thanks

    Wednesday, September 5, 2012 6:38 PM
  • Steve,

    Not entirely:

     

      • First update your current MIIS 2003 SP1 to SP2
      • Then export your database from SQL 2000 and import it in a SQL 2008 server. Do this by following these steps:

       

      1. Backup the MicrosoftIdentityIntegrationServer database
      2. Detach the MicrosoftIdentityIntegrationServer database from the backend SQL Server
      3. Copy/Move the MDF and LDF files to the SQL Server 2005 machine
      4. Attach the MDF file to the SQL Server 2005 instance and let the database be converted
      5. Detach the database from the SQL Server 2005 instance
      6. Copy/Move the MDF and LDF files to the SQL Server 2008 instance
      7. Rename the MDF file to FIMSynchronizationService.MDF
      8. Rename the LDF file to FIMSynchronizationService_log.LDF
      9. Attach the MDF file to the SQL Server 2008 instance

     

    • Install FIM 2010 on a new, 64bit, server and during installation, point to the created database.
    • Copy the 'Extensions' folder from the old server, to the new one. (recommended: recompile the dll's to 64-bit).
    • Optional, but recommended: update to FIM 2010 R2.


    Because you copied the database, the management agents and all your MIIS configurations are already present in FIM.


    Best regards,
    Pieter de Loos.


    Pieter de Loos - Consultant at Traxion (http://www.traxion.com) http://fimfacts.wordpress.com/




    Thursday, September 6, 2012 6:24 AM
  • For upgrading MIIS 2003 SP1 to SP2, it needs to be have

    • Microsoft SQL Server 2000 with Service Pack 3a (SP3a) or higher
    • Microsoft Visual Studio 2005

    However, in our environment we have SQL Server 2000 with SP2 and Microsoft Visual Studio 2003. That is the reason we are thinking of doing it directly without updating to SP2.

    Thanks

    Thursday, September 6, 2012 7:16 AM
  • What is the best practice to have the FIM Synchronization database locally or on the clusyter SQL server. If it is placed on cluster then if database size is more, than it takse lot of time for synching. Please suggest if there is any best practice for the same.

    Thursday, September 13, 2012 8:59 AM