Import a Server Configuration From File

For this procedure, you can import (open) a Microsoft® Forefront Identity Manager (FIM) 2010 R2 server configuration from file. A server configuration also includes all management agents that exist when an export server configuration file is created. This can be helpful when you want to import or recover a known-good server configuration and is the preferred method when migrating a server configuration. To complete this procedure, you must be logged on as a member of the FIMSyncAdmins security group..

Caution - Do not run Windows Management Instrumentation (WMI) scripts when importing a server configuration. Failure to do so might cause a management agent run to fail or corrupt a management agent configuration.

To import a server configuration from file

1. On the File menu, click Import Server Configuration.

2. In Browse for folder, click the location of the file to be imported.

3. For each directory-based management agent, Management Agent Designer checks the connected data source schema and creates a list of existing partitions. Management Agent Designer then attempts to match those existing partitions with partitions specified in the management agent configuration file. If partition matches can be guaranteed with matching globally unique identifiers (GUIDs) and matching names, no action is necessary. If partition matches cannot be guaranteed, the Partition Matching dialog box appears for more information:

   • By default, if partitions are detected in the management agent configuration file, and those partitions have a matching GUID with an existing partition, they are not displayed.

     To display partitions with an exact match, click Show exact partition matches. Exact partition matches detected by Management Agent Designer are shown for reference only. No additional action for exact matches is necessary.

   • If partitions are detected in the management agent configuration file and those partitions do not have a matching GUID with an existing partition, but do have a matching name, they are proposed as a match.

     Deselect the unwanted partitions, and then click OK.

   • If partitions are detected in the management agent configuration file, and those partitions do not have a matching GUID or a matching name with an existing partition, you must match them manually.

     To match them manually, click the partition in File Partition, click an existing partition in Existing Partition, and then click Match.

   • Deselected partitions are not available for processing in a run profile.

     To deselect an existing partition, click the partition in Existing Partition, and then click Deselect.

   • To remove a proposed match, manually matched, or deselected partition in Matched Partitions, click the partition, and then click Remove.

Important

When you import a server configuration from file, existing management agents (with the same name and GUID) are replaced by management agents from the imported server configuration. The existing metaverse schema will be appended with the imported metaverse schema. It is recommended that you import only a fully tested server configuration.

Important

The FIM 2010 Synchronization Service account must have read/write permissions to the target folder or file when importing a server configuration.

Note

The Partition Matching dialog box does not appear for text file management agents when importing a server configuration. Text file management agents do not have a native connected directory partition schema. Text file partitions exist only as logical groupings within a management agent.

See Also

Concepts

Export a Server Configuration to File
Svrexport: Server Configuration Export Tool
Import a Management Agent from File