-
Title
Installation of DSA fails - possible workarounds -
Description
Installation of DSA via RDP fails with different errors.
Are there any other ways or workarounds to deploy the DSA? -
Resolution
If installation of DSA via RDP fails then DSA can be installed locally.
Before installing DSA manually, please open Server Manager, Roles and Features, go to Features section and make sure that the following pre-requisites are installed: .NET 3.5 and Message Queueing
Open file explorer and browse to the \DSASetup directory on the Console server: \\<QMM_ConsoleServer>\DSASetup.
Run DSA.msi.
When connecting to ADAM project, specify the computer name where ADAM is installed (NETBIOS name) and specify the port.
By default ADAM uses the port 389. To confirm all the ADAM settings, click on Project | Open Project in the Console and review the tab 'Configure AD LDS Project'.Also note the service account used in the tab 'Set Auxiliary Account'
After connecting to the existing project, the new DSA can be used.
If not visible from Project (Tools - Agents) close and re-open Agent Manager or just refresh the view and new DSA computer should appear there.
It is a good idea to specify preferred DC and GC for the newly installed agent. For more details please review KB article 14630:
https://support.quest.com/SUPPORT/index?page=solution&id=SOL14630