How to migrate and upgrade the application using a remote SQL installation (4281119)

Upgrade steps for Desktop Authority (DA), including the migration of DA to a new server.

NOTE: These steps ONLY apply to a remote installation of SQL that is not on the original DA server, or the new DA server.

NOTE:  If upgrading to 10 or above, it is necessary to upgrade to 9.3 first. 

2.  Install Desktop Authority on the new server. During installation, point to the existing SQL Server instance used by the previous version.

3.  Copy over the SLStart.ini file from C:\Program Files(x86)\Quest\Desktop Authority\Desktop Authority Manager\Scripts on the original DA Server to the new DA Server.
      This file contains current Global Options settings, such as Exceptions and diagnostic logging settings.
      To preserve the Global Options settings copy the SLStart.ini file from the original DA Server to the same location on the new DA Server

5.  On the new DA Server open 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".

6.  Go to Deployment Settings | Server Manager | Service Management. Verify that the Administrative Service (and Update Service if it’s installed) is in “Started” status.

7.  Click on the drop-down next to "Replicate changed files (default)", select the option "Force and update of the local Desktop Authority folder on clients", click “Yes” if prompted. When that is complete Replicate the changes. 

Note: Both servers have a share called SLScripts$. To avoid issues, it's best to disable this share on the original server if the server is to remain in the domain.