How to migrate to a SQL Configuration Store (4318648)

Configuration store requirements:

SQL Server (Supported version include 2012, 2012R2, 2014, 2016, 2017 and 2019)


Migrating from AD/AD LDS to a SQL configuration store:

https://support.quest.com/technical-documents/gpoadmin/5.16/user-guide/6#TOPIC-1686441

Important: Run the config utility first using the /T switch for testing only to see if any errors occur

Steps for the actual migration

Open the GPOADmin console and right click the forest and choose Re-configure Version Control Server.

Select the SQL Server ( You do not need to create the database. It will be created by GPOADmin with the name you define here).

Choose the location for backups. The Migration utility migrates configuration store data; it does not migrate backups. To ensure the migration completes without issue, it is recommended to continue to use the same backup store.

After configuring the SQL database, migrate data to the new SQL database.

*IMPORTANT* The configuration utility must be:

• • Run on the GPOADmin server host computer.
• • Run as an account that has access to the AD LDS configuration store and the new SQL Database. In most cases this will be the service account.
• Pointed to a GPOADmin 5.14 or above configuration storage location.
• • After the migration, restart the Watcher Service so that it will use the correct configuration Store.

Open an elevated command prompt and navigate to: C:\Program Files\Quest\GPOAdmin and execute the below command:

ConfigMig.exe GPOAdminServer.FQDN /T (IMPORTANT!!! Use T for a test run. If you run it without switches, it will migrate everything. For more switches,  run the command “ConfigMig.exe” on its own.)

Once finished, restart the watcher service.