Configuration Migration Deployment Guide
Applies To: Forefront Identity Manager 2010
You can migrate the configuration settings that are stored in Microsoft® Forefront® Identity Manager (FIM) 2010 from one environment to another. This process enables end users to configure and validate FIM 2010 configuration in a pilot environment and then automatically apply this configuration to a production environment.
In order to migrate from one environment to another, the builds for both the source and the target servers must be identical.
What This Document Covers
This document describes the steps for migrating configuration data in the FIM Service and the FIM Synchronization Service. This document does not describe the steps for the Forefront Identity Manager Certificate Management (FIM CM) or FIM Add-ins and Extensions. This document assumes familiarity with FIM 2010.
This document does describe migration of:
FIM Synchronization Service management agent and metaverse configuration.
Custom dynamic-link libraries (DLLs) that are used in custom workflow activities.
FIM Service configuration objects, which include policy, schema, and portal configuration.
This document does not describe migration of:
Configuration settings that are applied by installion of a feature or component.
Configuration settings that are stored in FIM CM.
Configuration settings that are stored in the registry.
Client components, such as the FIM Add-in for Microsoft Office Outlook® or the FIM Password Reset Client.
Configuration settings and client features are restored by running Setup again. Manually editing the registry or application configuration files is not described in this document. Custom DLLs must be restored by using the recommended procedures that the DLL vendor supplies.
The scenario in this document uses the Windows PowerShell™ command-line interface scripts that are listed in Appendix A: Windows PowerShell Scripts. You can use these scripts without modification on the local server running FIM 2010. However, we highly recommend that you review the scripts and understand what they are doing before you run them. For a detailed explanation of the scripts, see Appendix B: Annotated Scripts.
For an overview of FIM 2010 documentation and guidance for using it, see the Documentation Roadmap.
This document is intended for information technology (IT) planners, systems administrators, system architects, technology decision-makers, consultants, infrastructure planners, and IT personnel.
This document assumes that you have a basic understanding of FIM and Windows PowerShell. Furthermore, this document assumes familiarity with the conceptual overview of the FIM 2010 R2 Service configuration.
You can complete the procedures in this document in about two hours with a default installation. This time estimate includes reading this document. The actual time for a production system depends on the amount of data, network connections, and server hardware. A system with terabytes of data could possibly take longer than six hours to complete the procedures.
The product team would like to thank the Technology Adoption Program (TAP) and Rapid Deployment Program (RDP) participants who helped test this document in their environments. Their feedback was invaluable. In addition, the product team would like to thank Markus Vilcinskas for his advice regarding the scripts.
Where to Get Help
If you encounter issues that are not addressed in this document, use the FIM forum (http://go.microsoft.com/fwlink/?LinkID=163230) resources for assistance. The FIM 2010 R2 forum brings together experts from the community to collaborate on FIM 2010 R2 topics. These community members may be able to help answer your questions.
For examples of other Windows PowerShell scripts, see the FIM ScriptBox (http://go.microsoft.com/fwlink/?LinkID=163230). The FIM ScriptBox contains community-generated scripts for accomplishing many common tasks.
Sections in This Document
This document includes the following sections:
Appendix C: Troubleshooting
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