none
Scale out existing FIM 2010 R2 Infrastructure RRS feed

  • Question

  • Hello All,

    I have a FIM Lab set up that is all contained in one box. I was wondering how do I go about scaling this out to several boxes.

    Sync on its own box
    Self service register/reset on its own box
    FIM Portal on its own box.
    SQL on its own box.

    Currently all these roles reside on the same server. How do I go about migrating them to different boxes without starting from scratch.

    Any advise/suggestions is greatly appreciated.

    Tuesday, October 13, 2015 6:11 PM

Answers

  • High level, here is what you need.

    1. Install a new SQL Server and Copy the Databases there. 

    2. Install FIM Synchronization on a new server.  Choose existing DB during install and point to the DB you migrated.

    3. Install FIM Service\Portal on a new server.  Choose existing DB during install and point to the DB you migrated.

    4. Install SSPR on a new Server.  Choose existing DB during install and point to the DB you migrated.

    This is how you get to keep the data, but since it is a DEV and there is still lot of work either way, I would simply built a new ENV and do a Migration Style from the current one.


    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Nosh Mernacaj Wednesday, October 14, 2015 4:38 PM
    • Marked as answer by sanoske312 Wednesday, October 14, 2015 4:39 PM
    Tuesday, October 13, 2015 7:15 PM
  • High level, here is what you need.

    1. Install a new SQL Server and Copy the Databases there. 

    2. Install FIM Synchronization on a new server.  Choose existing DB during install and point to the DB you migrated.

    3. Install FIM Service\Portal on a new server.  Choose existing DB during install and point to the DB you migrated.

    4. Install SSPR on a new Server.  Choose existing DB during install and point to the DB you migrated.

    This is how you get to keep the data, but since it is a DEV and there is still lot of work either way, I would simply built a new ENV and do a Migration Style from the current one.


    Nosh Mernacaj, Identity Management Specialist

    Couple additions from my perspective:

    1. You'll also need to bring the SQL Agent jobs over

    3. You may have some trouble doing this if the existing FIM Service/Portal has been patched. You can install the old version, point it to a temporary (new) database, patch it to the same level as the existing database, and then reconfigure it to use the original database.


    Thanks, Brian

    • Marked as answer by sanoske312 Wednesday, October 14, 2015 4:39 PM
    Wednesday, October 14, 2015 4:09 PM
    Moderator

All replies

  • High level, here is what you need.

    1. Install a new SQL Server and Copy the Databases there. 

    2. Install FIM Synchronization on a new server.  Choose existing DB during install and point to the DB you migrated.

    3. Install FIM Service\Portal on a new server.  Choose existing DB during install and point to the DB you migrated.

    4. Install SSPR on a new Server.  Choose existing DB during install and point to the DB you migrated.

    This is how you get to keep the data, but since it is a DEV and there is still lot of work either way, I would simply built a new ENV and do a Migration Style from the current one.


    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Nosh Mernacaj Wednesday, October 14, 2015 4:38 PM
    • Marked as answer by sanoske312 Wednesday, October 14, 2015 4:39 PM
    Tuesday, October 13, 2015 7:15 PM
  • High level, here is what you need.

    1. Install a new SQL Server and Copy the Databases there. 

    2. Install FIM Synchronization on a new server.  Choose existing DB during install and point to the DB you migrated.

    3. Install FIM Service\Portal on a new server.  Choose existing DB during install and point to the DB you migrated.

    4. Install SSPR on a new Server.  Choose existing DB during install and point to the DB you migrated.

    This is how you get to keep the data, but since it is a DEV and there is still lot of work either way, I would simply built a new ENV and do a Migration Style from the current one.


    Nosh Mernacaj, Identity Management Specialist

    Couple additions from my perspective:

    1. You'll also need to bring the SQL Agent jobs over

    3. You may have some trouble doing this if the existing FIM Service/Portal has been patched. You can install the old version, point it to a temporary (new) database, patch it to the same level as the existing database, and then reconfigure it to use the original database.


    Thanks, Brian

    • Marked as answer by sanoske312 Wednesday, October 14, 2015 4:39 PM
    Wednesday, October 14, 2015 4:09 PM
    Moderator
  • Thank You Brian.

    Wednesday, October 14, 2015 4:40 PM
  • Thank you Nosh
    Wednesday, October 14, 2015 4:40 PM
  • You are welcome! Good Luck!

    Nosh Mernacaj, Identity Management Specialist

    Wednesday, October 14, 2015 6:44 PM