How to associate another Directory Synchronization Agent to Migration Sessions and Directory Sync (4262095)

How can jobs or migration sessions associated with particular Directory Synchronization Agents be moved to other Directory Synchronization Agents?

UpdateJob2AgentAssociations script can be used to move directory synchronization jobs to a new DSA server without performing full re-sync. Also this script allows to re-assign finished migration sessions between DSA servers to preserve rollback functionality.

The UpdateJob2AgentAssociations script can be downloaded at the bottom of the page.

Once downloaded, please un-zip the utility.

To install the script, complete the following steps:

1. Complete all migration sessions performed by the previous agent.
2. Stop all synchronization jobs being processed by the previous agent.
3. Deploy a new agent from Agent Manager.
4. Copy all files from%\Program Files%\Quest Software\Migration Manager\DSA\CONFIGS\Cache folder on the previous server to the corresponding folder on the new server.
5. Copy all files from%Program Files%\Quest Software\Migration Manager\DSA\CONFIGS\UndoStorage folder on the previous server to the corresponding folder on the new server.
6. Update the job-to-agent associations in the ADAM project database using the script. To do this, complete the following steps:
   1. Log on to the computer on which the ADAM database is located with an account that has administrative rights over the ADAM project partition.
   2. Run the UpdateJob2AgentAssociations.vbs file from the command line in the following format:

   cscript UpdateJob2AgentAssociations.vbs ADAMServer[:ADAMPort] ProjectName OldAgentName NewAgentName

   Where:

   -Path.The full path to the UpdateJob2AgentAssociations.vbs file.

   -ADAMServer. The name of the server running an ADAM instance with the migration project partition.

   -ADAMPort. ADAM instance port number (the default value is 389).

   -ProjectName. The name of the migration project to update. This name is displayed in the status bar of the Migration Manager Console.

   -OldAgentName.The NetBIOS name of the computer running the previous Directory Synchronization Agent.

   -NewAgentName.The NetBIOS name of the computer running the new Directory synchronization Agent.

   Example:

   cscript C:\UpdateJob2AgentAssociations.vbs ROM2003SRV6:50000 QMMADProject W2K3SRV1 W2K3SRV2

   Note:You must specify the full path to the UpdateJob2AgentAssociations.vbs file.

7. Uninstall the previous agent from Agent Manager.
8. Start all previously stopped directory synchronization jobs. To do this, right-click each jobs node in the the Migration Manager Console and select Start. The new agent will continue directory synchronization from the point it was stopped without full re-synchronization.

Logging

You can check the script execution results by viewing the UpdateJob2AgentAssociations.log file located in the script installation folder.