Return
-
Title
Slowly migrate Desktop Authority to another server -
Description
This implementation assumes that a secondary KACE Desktop Authority server is running. For further information about deploying DA, visit the following article: how to install desktop authority 9.X
To simplify, please consider the following terminology:- DC= Domain Controller
- DA= Desktop Authority.
- DA1= Old Desktop Authority server.
- DA2= New Desktop Authority server which we are migrating to.
- CBM= Computer shared folder
- UBM= User shared folder
A. Introduction
The traditional methods explained below to migrate Desktop Authority, sometimes are not an option for IT managers:1. Export profiles from the old server, then import them to the new server2. Backup database of the old server and restore it to the new one2.1 if DB is locally stored: how to migrate DA and it's local DB to another server.
2.2 if DB is externally stored: how to migrate and upgrade the application using a remote SQL installationThis document contains information on an alternative option to accomplish the migration.The process will allow IT, managers, customers, or clients to selectively migrate users and computers to the new DA according to their needs, which will allow them to test elements or entire profiles on the new server before the implementation for production.Also, if IT managers have older operating systems for their client machines, and existing DA runs older scripts or registry changes, none comparable to newer OS or build version, and if they are gradually upgrading the operating systems, this option will allow them to create new elements on a new Desktop Authority, and then slowly migrate the client machines according to the upgrade completes.Important note: Quest Kace Desktop Authority documentation is intended for migration or Dev purposes. Only 1 production server is allowed.
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.