Return
-
Title
Migrate GPOAdmin SQL Database to a new SQL server -
Description
Migrate GPOAdmin SQL Database to a new SQL server -
Resolution
Migrating the GPOADmin SQL database to a new SQL serve can be done with the following steps:1- Verify/Note security on the GPOADmin database2- Move the database files3- Rebuild security on the new SQL server.For a more detailed outline:Step 1-Check the security on the GPOADmin database in SQL server.Note any accounts associated with the GPOADmin database (typically this would only be the service account and one administrator).Check the security principals on the database server itself for these accounts and note how they are mapped to the GPOADmin database.Any security here must be replicated on the new database server.Step 2 -Get the properties of the GPOADmin database, and note the location and names of the database files.Detach the GPOADmin database.Copy the data files for the database to the new SQL server.Attach a database on the new server, selecting the copied GPOADmin database files.Step 3 -Now that the GPOADmin database exists, rebuild the security on the database in the same manner as noted in Step 1.IMPORTANT:
Please confirm under Options > Storage > Backup location if SQL is used as your GPOADmin backup storage location as seen below:
If yes, then make sure to migrate QGPM_Backups database to your new SQL server as well using the same process described above to migrate your main GPOADmin database. Failing to do so may impact your GPOADmin server in a way that would not allow you to modify your existing GPOs. You may find this QGPM_Backups database in your old SQL server under Databases:
After these steps are completed, select to "re-configure version control root" GPOADmin to point its configuration store and backup storage to the new SQL database server.