Instructions on how to migrate the GPOADmin service to another server.
Here are the steps to go forward with moving the GPOADmin service to another server
1. Stop the existing GPOADmin service.
2. Install GPOADmin on another server
3. Begin the configuration of GPOADMin and connect to the same ADLDS instance, or SQL database and the same network storage for GPO backups.
4. Once it is started, check to make sure everything is working before completely uninstalling GPOADmin on your older server.
The above assumes that once the product is installed in a new server it will be connected back to the same or existing configuration store (AD LDS or SQL DB) and backup store (Network Share or SQL DB). However, if the configuration store has to be migrated to a new server as well, then depending on your current configuration store you may follow the steps from KB articles listed below first before migrating your GPOADmin product to a new server. Once the configuration store migration is complete you may perform the above 4 steps to migrate your GPOADmin product to the new server.
KB Articles to migrate configuration store:
Migrate GPOADmin SQL Database to a new server: https://support.quest.com/gpoadmin/kb/4276835/migrate-gpoadmin-sql-database-to-a-new-sql-server
Migrate AD LDS to a new server: https://support.quest.com/kb/4328150/how-to-migrate-an-existing-gpoadmin-ad-lds-configuration-to-a-new-instance
And the following KB article provide steps if you want to migrate from AD LDS to SQL Database: https://support.quest.com/kb/4318648/how-to-migrate-to-a-sql-configuration-store
,
