For this procedure, you can import (that is, open) a management agent from file. You can use this procedure to import a known-good management agent. To complete this procedure, you must be logged on as a member of the FIMSyncAdmins security group.
|
To import a management agent from file |
-
On the Tools menu, click Management Agents.
-
On the Actions menu, click Import Management Agent.
-
Click the management agent configuration file that you want to import, and then click Open.
-
For call-based management agents, Management Agent Designer checks the connected data source's schema and creates a list of existing partitions. Management Agent Designer 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 will appear and require any of the following:
- 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, select 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 they do have a
matching name, they are proposed as a match and no additional
action is necessary.
- 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, they
must be matched manually by clicking the partition in File
Partition, clicking an existing partition in Existing
Partition, and then clicking Match.
- To deselect an existing partition, click the
partition in Existing Partition, and then click
Deselect. Deselected partitions are not available for
processing in a run profile.
- To remove a proposed match, manually matched,
or deselected partition in Matched Partitions, click the
partition, and then click Remove.
- 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, select 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.
|
Caution |
|
Do not run Windows Management Instrumentation (WMI) scripts when updating a management agent. Failure to do so might cause a management agent run to fail or corrupt a management agent configuration. |
|
Note |
|
When importing a management agent configured as a source for password synchronization, if the source management agent refers to target management agents, those target management agents must already exist. If a referred-to target management agent does not already exist, those referenced by the source managmement agent will be deleted from the source management agent's configuration and the associated partition will no longer be enabled for password synchronization. |
|
|
Note |
|
The Partition Matching dialog box does not appear when you import a text file management agent. Text file management agents do not have a native connected data source partition schema. Text file partitions exist only as logical groupings within a management agent. |
|
|
Note |
|
A management agent configuration file that you use to update a management agent is the same as a management agent configuration file that you use to import a management agent. You create the management agent configuration file when you export a management agent. For more information, see See Also. |
|
|
Note |
|
When you export a management agent, it is saved in XML format and has an .xml file name extension. The management agents associated connector space and any objects within are not saved with the export file. |
|
|
Note |
|
When you import a management agent by using this method, you actually create a new management agent. The management agent cannot already exist (except as an exported .xml file) on the server. The new management agent is created with all of the settings and properties that were configured in the exported management agent. A new connector space is created after the management agent is run for the first time. The new management agent has a new GUID identifier, and the exported management agent remains intact. As a result, you can use the exported management agent as a template for additional management agents. To import a management agent from file without creating a new GUID identifier, see Update a Management Agent from File. By updating a management agent, you retain an existing management agent's associated connector space. |
|
|
Note |
|
When you import a management agent from file, you need to complete each step of the Management Agent Designer, even though all of the settings that existed in the management agent when it was exported to file are retained. All run profiles associated with a management agent are also imported with no additional configuration necessary. |
|
|
Note |
|
When you import a management agent for Active Directory from file and you change the Active Directory forest configuration settings, the run profile settings are not retained. |
|
|
Note |
|
You can also use the command-line tool, Maexport, to import a management agent from file. |