For this procedure, you can update a management agent from an exported (that is, saved) file. This feature can be useful when you want to update a management agent on a production server with changes made to the same management agent on a test server. To complete this procedure, you must be logged on as a member of the FIMSyncAdmins security group.
|
To update a management agent from file |
-
On the Tools menu, click Management Agents.
-
In Management Agents, click the management agent that you want to update.
-
On the Actions menu, click Update Management Agent.
-
Select the management agent configuration file you want to use, and then click Open.
-
For all management agent types, Management Agent Designer will attempt to match existing partitions of the management agent being updated with those partitions specified in the management agent configuration file. If those partition matches can be guaranteed with matching globally unique identifiers (GUIDs) and matching names, no action is necessary. If those partition matches cannot be guaranteed, the Partition Matching dialog box will appear and requires any of the following:
- By default, if partitions are detected in the
management agent configuration file, and those partitions have a
matching GUID with partitions in the existing management agent,
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 partitions in the existing management agent, but
do have a matching name, they are proposed as a match and no
additional action is necessary.
- For file-based management agents, if
partitions are detected in the management agent configuration file,
and those partitions do not have a matching GUID or a matching name
with partitions in the existing management agent, they must be
added manually by clicking the partition in File Partition,
and then clicking New or they are matched by clicking a
partition in Existing Partitions, and then clicking
Match.
- For directory-based management agents, if
partitions are detected in the management agent configuration file,
and those partitions do not have a matching GUID or a matching name
with partitions in the existing management agent, they must be
matched manually by clicking the partition in File
Partition, then clicking an existing partition in Existing
Partition, and then clicking Match.
- For file-based management agents, you can
delete a partition in the existing management agent by clicking on
the partition in Existing Partition, and then clicking
Delete. Deleted partitions no longer exist after the
management agent has been updated.
- To remove a proposed match, or manually
matched 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 partitions in the existing management agent,
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 you update a management agent. If you run WMI scripts when you update a management agent, it might cause a management agent run to fail or corrupt a management agent configuration. |
|
Important |
|
For management agents for Active Directory global address list (GAL), when updating a management agent from file, the test server (the server that exported a management agent to file) and the production server (the server being updated) must have the same management agents for Active Directory GAL. In addition, the contact types for each management agent on each server must match. Failure to do so may cause export attribute flow rules to fail where references to a contact type may not exist. |
|
|
Important |
|
When you export a management agent to file, any associated rules extensions are not saved. When you update a management agent from file and changes are made to any associated rules extensions, you must update the rules extensions separately. In addition, FIM does not save the associated connector space and connector space objects. When you update a management agent from file, the associated connector space of the existing management agent will be retained, however, the management agent must be run with a Full import and Full Synchronization run profile to apply changes and update the connector space. |
|
Note |
|
For directory-based management agents, when matching partitions, not all partitions will be available in the File Partition list box. Only those directory partitions selected on the Configure Directory Partitions page in Management Agent Designer when the management agent was created will be available. |
|
|
Note |
|
For directory-based management agents, when matching partitions, only those directory partitions available in the File Partition list box (Those selected on the Configure Directory Partitions page in Management Agent Designer when the management agent was created) will have their relevant partition configuration migrated to the existing partition. If there are configuration changes to unselected partitions, even though they may match an existing partition by GUID, the partitions are filtered and changes are ignored. |
|
|
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. |