none
Migrating FIM Portal configuration? RRS feed

  • Question

  • Hi,

    We have tried the Microsoft approach, but it doesnt migrate everything (http://technet.microsoft.com/en-us/library/ee534906%28v=ws.10%29.aspx) - there is a problem with the MA GUIDs, so all the Sync Rules have to be recreated - and there typically is a lot more errors that I just cant remember at the moment.

    Is there a way to export just the MPRs or Sets, or Sync Rules or Workflows by themselves? And in turn import just the MPRs, or Workflows, etc?

    Would be great to be able to export them to a Powershell object, for clean import later.

    thanks



    • Edited by Shim Kwan Friday, May 16, 2014 3:36 AM
    Friday, May 16, 2014 2:33 AM

All replies

  • Check this article.

    http://technet.microsoft.com/en-us/library/ff400277(v=ws.10).aspx


    Friday, May 16, 2014 4:46 AM
  • Dan - your URL points to the same solution I had in my post. We are looking for an alternative method.
    Friday, May 16, 2014 5:22 AM
  • It's been a while sinve I've had to do it but I think that after you've run the export powershell scripts and you've got the file to import, open the file and replace the MA GUIDS with the ones in the new environment.
    Friday, May 16, 2014 5:27 AM
  • Good idea - maybe that's all I need to do then, will certainly try that route :)

    Now I have spotted this method: http://www.integrationtrench.com/2011/07/convert-fim-exportobject-to-powershell.html

    Just cant get it to work...has anyone successfully done this, and what were your steps please?

    thanks

    Friday, May 16, 2014 5:39 AM
  • That post is pretty old and since then he's put that code into a PowerShell module that you can use. There's a link at the top right of his blog. http://fimpowershellmodule.codeplex.com/

    It can be useful if you want to query via PowerShell for something like automated testing but in a migration scenario I don't think it's going to make things any easier for you.

    Friday, May 16, 2014 5:44 AM
  • Hello,

    If you want to export all FIMConfig from an integration environment to a production environment, the basic step are:

    • Import FIMService Schema from integration environment
    • Import FIMService Schema from production environment
    • Compare the two schema
    • Export the Schema result to production environment
    • Import FIMService Portal from integration environment
    • Import FIMService Portal from production environment
    • Compare the two Portal
    • Export the Portal result to production environment
    • Save FIMSync Server config from integration environment
    • Apply FIMSync Server config to production environment
    • Import FIMService Policy from integration environment
    • Import FIMService Policy from production environment
    • Compare the two Policy
    • Export the Policy result to production environment

    You can use this script for import/export FIMService config http://technet.microsoft.com/en-us/library/ff400275%28v=ws.10%29.aspx

    Regards,


    Sylvain

    Friday, May 16, 2014 7:58 AM
  • Will definitely try this approach, thanks Sylvain.
    Monday, May 19, 2014 7:03 AM
  • You guys haven't seen this nice tool by Rex, you can choose what objects to migrate in tick boxes. 

    http://www.css-security.com/blog/simplifying-fim-service-migration/

    Monday, May 19, 2014 12:25 PM
  • This looks great Sameera - will try it out this week!
    Monday, May 19, 2014 11:25 PM
  • I used the tool that Rex made just this week to migrate to Production. It worked great. Just be sure to export the schema before the policy and you should be good to go. I only had four errors on an export (and they were my fault for forgetting to tick a particular set to export). The migration took all of 30 minutes. Not bad considering most of that time was running the scripts to get the production and dev schema and policy XML files.
    Wednesday, May 21, 2014 9:57 PM
  • Hi,

    Two week ago, I have realized a full migration between cross forest.

    I create a post on my blog (in french), but there are lot of screenshot.

    http://www.it-channels.com/forefront-identity-manager/139-fim-sync-fim-service-sauvegarde-et-restauration-fim-backup-restore

    Regards,

    Joris


    Joris Faure

    Wednesday, May 21, 2014 11:42 PM
  • Actually I updated a tool that someone else wrote and updated the scripts that Microsoft wrote, but I did put together a nice process around the updated tool and scripts. The process has been effective for several of our clients. Do check out the blog post at https://blog.css-security.com/blog/simplifying-fim-service-migration and give it a try.

    Rex




    • Edited by Rex Wheeler Friday, April 1, 2016 4:10 PM Fixed Link
    Thursday, May 22, 2014 3:27 AM
  • Hi,

    FYI the post is available at this URL now:

    https://blog.css-security.com/blog/simplifying-fim-service-migration

    One problem: I can't find the zip file that contains the updated Microsoft scripts. The following link does not work anymore:http://www.css-security.com/fdist/FimServiceMigration1.3.zip

    Does anyone know where I can find it?

    Matthieu

    Friday, April 1, 2016 9:17 AM
    • Edited by SamiVV Friday, April 1, 2016 3:53 PM
    Friday, April 1, 2016 3:52 PM
  • Looks like that link got broken when we updated our website. I will see if we can get it fixed. Those scripts are part of the project up on GitHub, so in the meantime, you can grab them from:

    https://github.com/RexWheeler/FIMDelta/tree/master/build

    Rex


    • Edited by Rex Wheeler Friday, April 1, 2016 4:02 PM Made the link a link
    Friday, April 1, 2016 4:01 PM
  • Perfect guys, thanks a lot for your help!

    Matthieu

    Sunday, April 3, 2016 12:33 PM