-
Title
Directory Synchronization Agent is not working as expected - what can be done? -
Description
Often Quest Technical Support is contacted with issues or questions where customer is almost positive that the installed software has been damaged due to a configuration or maintenance mistake but is unsure how to proceed and would like to know what is the best way to resolve the issue without impacting the existing migration.
-
Resolution
One of the most important troubleshooting steps is to isolate the issue and to narrow the troubleshooting.
Synchronization is performed by DSA which utilizes the existing project and works according to the settings specified in project (ADAM), it is important to determine whether the problem is caused by DSA or by ADAM.
The most elegant way to verify whether DSA is working correctly or not is to install a new separate DSA instance, and use this new instance during migration or synchronization.
To install a new agent in QMM navigate to Tools - Agents and use the wizard, follow the steps.
The machine on which the agent will be installed should meet the software requirements, which are outlined in the QMM Quick Start Guide under the System Requirements section or in Release Notes. Before installing the agent on another server, you will need to enable the setting "Allow remote users to connect to this computer". This is a prereq for remote agent installation.
After the new agent was successfully installed during next migration an additional step (option) will appear which will allow to select one of the existing agents.
Under synchronization properties, the agent can be changed as well, this has to be done when synchronization is stopped. This change (as any change to synchronization job properties) will require a full resynchronization.
After verifying the new DSA instance works as expected the old instance can be removed or re-installed if the agent needs to be used on the original DSA computer.
**Important note: if an agent has been uninstalled, all migration sessions which were performed using this particular agent can not be undone. Keeping this in mind, it is a good idea to leave the agent in place until migration is finished. Or to copy and preserve the UndoStorage folder, which contains the Undo information for old migration sessions.**
Notes:
After installing a new agent ensure the preferred DC and GC are specified, this can be done using the same menu under Tools- Agents. For detailed instructions see KB article 14630:
https://support.quest.com/SUPPORT/index?page=solution&id=SOL14630
In bigger environments is strongly recommended to not install the DSA on the same machine where ADAM is installed.
Agents do not have to be installed on the same machine where QMM is installed, the DSA can be installed on any other machine, not necessary on the QMM console machine. Using different computers for ADAM, DSA and QMM console provides some relief in a disaster scenario, when eg. the console crashes.
One of the most important troubleshooting steps is to isolate the issue and to narrow the troubleshooting.
Synchronization is performed by DSA which utilizes the existing project and works according to the settings specified in project (ADAM), it is important to determine whether the problem is caused by DSA or by ADAM.
The most elegant way to verify whether DSA is working correctly or not is to install a new separate DSA instance, and use this new instance during migration or synchronization.
To install a new agent in QMM navigate to Tools - Agents and use the wizard, follow the steps.
The machine on which the agent will be installed should meet the software requirements, which are outlined in the QMM Quick Start Guide under the System Requirements section or in Release Notes. Before installing the agent on another server, you will need to enable the setting "Allow remote users to connect to this computer". This is a prereq for remote agent installation.
After the new agent was successfully installed during next migration an additional step (option) will appear which will allow to select one of the existing agents.
Under synchronization properties, the agent can be changed as well, this has to be done when synchronization is stopped. This change (as any change to synchronization job properties) will require a full resynchronization.
After verifying the new DSA instance works as expected the old instance can be removed or re-installed if the agent needs to be used on the original DSA computer.
**Important note: if an agent has been uninstalled, all migration sessions which were performed using this particular agent can not be undone. Keeping this in mind, it is a good idea to leave the agent in place until migration is finished. Or to copy and preserve the UndoStorage folder, which contains the Undo information for old migration sessions.**
Notes:
After installing a new agent ensure the preferred DC and GC are specified, this can be done using the same menu under Tools- Agents. For detailed instructions see KB article 14630:
https://support.quest.com/SUPPORT/index?page=solution&id=SOL14630
In bigger environments it is strongly recommended to not install the DSA on the same machine where ADAM is installed.
Agents do not have to be installed on the same machine where QMM is installed, the DSA can be installed on any other machine, not necessary on the QMM console machine. Using different computers for ADAM, DSA and QMM console provides some relief in a disaster scenario, when eg. the console crashes.
-
Additional Information
If the DSA still fails to migrate or synchronize the directories, another troubleshooting method is to change the preferred DC/GC that is being used for the migraiton to another within the environment. Usually if the PDC emulator is the preferred choice. This can rule out any replication issues within the domains to be synchronized.