This article describes how to migrate Desktop Authority (with a local installation of SQL) to another server.
In this example, "Server1" has Desktop Authority installed with a local installation of SQL, and it will be migrated to "Server2" with another SQL installed locally.
Step 1:
Make a backup of the existing DAConfiguration and DAReporting databases located on Server1. Also, the license file (register.ini) file will be needed for the installation on Server2. This can be found in the Slogic$ share. Note: The register.ini file will not apply to version 11 and up. A new license file must be requested to Licensing.
Default Slogic$ location for version 10.x is C:\Program Files (x86)\Quest\Desktop Authority\Desktop Authority Manager
Step 2:
Install SQL on Server2 and restore the backed-up Desktop Authority databases to the instance of SQL running on Server2.
Step 3:
Install Desktop Authority on Server2 and point to the SQL instance created in Step 2. Close the Desktop Authority Manager Console.
Step 4:
To preserve the Global Options settings, copy the SLStart.ini file from the SLScripts$ share (C:\Program Files (x86)\Quest\Desktop Authority Manager\Scripts) on Server1. Go to the same location on Server2 and paste the file. This file contains current Global Options settings, such as Exceptions and diagnostic logging settings.
Step 5:
On Server2 launch the Desktop Authority Manager Console and go to Deployment Settings | Server Manager | Replication Options and check whether the "Source server" field contains the name of the new Desktop Authority Server, update it if needed by clicking on the "Edit" button, then "Save"
Step 6:
Check each User Profile's "Logging" object. (Client Configuration | Profiles | User | ProfileName | Logging)
Under the section "Log file location" make sure the Path is either set to the new server or cleared out and set to .
Step 7:
Go to Deployment Settings | Server Manager | Service Management. Verify that the Administrative Service (and Update Service if it’s installed) is in “Started” status. Then go to Replicate | Force an update of the local Desktop Authority folder on clients option, click “Yes” if prompted. When that is complete select Replicate | Replicate all, and click “Yes” if prompted.
Additional Information
If decommissioning Server1 it is recommended to turn it off after completion of the installation to Server2.
If planning to decommission later or repurpose Server1, it is recommended to stop the Desktop Authority IIS website and stop and disable the Desktop Authority Manager Service and the Desktop Authority Operations Service for uninstallation at a later time.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center