Chat now with support
Chat with Support

GPOADmin 5.18 - Quick Start Guide

Editing the Version Control server configuration store

Users logged on with an account that is a member of the GPOADmin administrators group can edit the type of configuration store.

Right-click the forest, and select Re-configure Version Control server.
In the Select a Configuration Store dialog, select Active Directory, AD LDS, or SQL Server for your configuration storage location.

The best practice is to use AD LDS as the configuration store. However, in large environments, SQL server is the recommended option. Quest uses the following criteria to define large environments:

These are guidelines and should not be considered as an exhaustive list.

Replacing the Version Control server configuration settings

In some cases, you may want to keep the majority of the Version Control server settings the same throughout the deployment and have only select settings unique for each server.

If this is the case, you can copy the settings from an existing sever and then update where required rather than having to enter all the settings required during a reconfiguration.

Right-click the forest, and select Copy Server Configuration.
Right-click the forest, and select Options to update where required.

Migrating from AD/AD LDS to a SQL configuration store

A configuration utility is available that allows you to migrate the configuration store to SQL from an AD/AD LDS. You can migrate all objects or specify users, custom folders, keywords, email templates, roles, domains, containers, version control items, scheduled deployments, synchronization targets and synchronization results data as required.

The output from the configuration utility is written to the screen as well as to a Migration.txt file located in the install directory.

Before migrating the configuration store, Quest suggests that you test the migration to ensure that all objects migrate according to your specifications. To validate the migration, run the command with the /t option. This gathers all the information that will be committed to the SQL database but does not commit any changes.

Step-by-step walkthrough

This step-by-step walkthrough takes you through a GPOADmin scenario that includes the following:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating