Migration Scenarios

Applies To: Forefront Identity Manager 2010

To perform the procedures in this document, your Microsoft® Forefront® Identity Manager (FIM) 2010 environment should have the following characteristics:

  • Production environment: The production environment should include a supported topology, a supported build, and actual objects and users.

  • Pilot environment: The pilot environment should be representative of the production environment. This environment should include a representative topology of the FIM Synchronization Service and the FIM Service, the same build number as production, and a representative set of objects and users. You should have user objects on which to test policies for different roles.

The steps and related procedures are in chronological order. However, depending on your situation, you may not have to complete all of the procedures in this guide. For example, consider the following differences between migrating settings to a new environment as opposed to an existing environment.

Scenario 1: Migrate a new configuration to a new environment

If you intend to migrate a configuration to a new instance of FIM 2010, which has not been configured, complete all the procedures in this document. At a high level, you must migrate the FIM Synchronization Service configuration (that is, management agents, Metaverse, and so on); install FIM 2010; migrate custom DLLs; and then migrate the FIM Service configuration (Sets, Management Policy Rules, and so on).

Scenario 2: Migrate changes to an existing environment

To make small changes to a FIM 2010 configuration in a production environment, you should test and validate changes first in a lab or pilot environment and then migrate the changes into a production environment.

If you intend to migrate changes from a pilot environment to a product environment, you only have to complete the procedures that are relevant to those changes. For example, you can skip step 4 because it is not necessary to install FIM 2010. Also, if the only changes occurred in the FIM Service, you can also omit such steps as installing the new environment or migrating the FIM Synchronization Service configuration.

See Also


Configuration Migration Deployment Guide
Configuration Migration Deployment Steps
Appendix A: Configuration Migration Windows PowerShell Scripts
Appendix B: Annotated Configuration Migration Windows PowerShell Scripts
Appendix C: Troubleshooting FIM Configuration Migration