Chat now with support
Chat with Support

GPOADmin 5.17 - 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.

To edit the configuration store
1
Right-click the forest, and select Re-configure Version Control server.
2
In the Select a Configuration Store dialog, select Active Directory, AD LDS, or SQL Server for your configuration storage location.
* 
NOTE: Configuration Store Selection

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:

•
Domains with more than 500 registered objects that run searches on a regular basis.
•
More than 500 registered containers.
•
Containers with objects nested more than 3 levels deep.

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

a
If you select Active Directory, select the Domain Controller (DC) to be the Version Control server, and click Next.
Any DC in any domain of the selected forest can be specified as the primary version control server. This server can be thought of as another FSMO role in the Microsoft sense (such as Schema master, PDC Emulator, and RID master).
GPOADmin is a directory-enabled application and all its application information is stored in the configuration container of Active Directory. Because of how the information is stored, all information is automatically replicated to all other DCs. However, the primary version control server is the authoritative source for all version control actions. If it goes offline, users cannot perform actions such as check-in a desired group policy object change until the problem has been rectified.
b
If you select AD LDS, enter the NetBIOS name of the computer you are installing to and the port number in the format: server_name:port, and click Next.
For example, gpoadmin_svr: 389.
* 
NOTE: The username/port/server (but not password) will be cached, so the next time you open the console you will not need to enter this information.
c
If you select SQL Server, choose the required SQL server, enter a name for the database, select the authentication method to access the server, and click Next.
* 
NOTE: SQL Server versions 2012, 2012R2, 2014, 2016, 2017, and 2019 are supported.
To connect as the current user, select NT Authentication.
To connect using SQL credentials, select SQL Authentication and enter the user name and password.
3
Click through the rest of the Service Configuration Wizard and click Finish.

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.

To edit the Version Control configuration using another servers settings
1
Right-click the forest, and select Copy Server Configuration.
2
Select the server configuration that you want to copy and click OK.
3
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.

* 
IMPORTANT: The configuration utility must be:
•
Run on the GPOADmin 5.16 server host computer.
•
Run as an account that has access to the AD/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 later configuration storage location. (Upgrade from versions older than 5.14 are not supported.)
•
After the migration, you need to restart the Watcher Service so that it will use the correct configuration store.
* 
NOTE: Before running the configuration utility, you need to configure the version control server to use SQL as the configuration store. See Editing the Version Control server properties to change the storage from
AD/AD LDS to SQL.

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.

To run the configuration utility:
•
From a command prompt, browse to and run Program Files\Quest\GPOAdmin>GPOADmin.ConfigMig.exe “FQDN of the AD/AD LDS server hosting the source configuration store.”
The following switches and options are available: (If none are specified, all objects are migrated.)
•
O = Service Options
•
U = Users
•
F = Custom Search Folders
•
K = Keywords
•
E = Email Templates
•
R = Roles
•
D = Domains
•
C = Version Control Containers
•
I = Version Control Items
•
S = Scheduled Deployments
•
T = Synchronization Targets
•
Y = Synchronization Results
•
/T = Testing only. Validates the object data from the source configuration store. Nothing is written to the database.
•
/H:<GPOADmin Host>] = The FQDN of the source GPOADmin host (Used to migrate Service Options stored in the registry)
•
/S:<domain\account> = The GPOADmin service account name. If not specified, the current user account is used.
•
/G = Grant the specified service account access.

Step-by-step walkthrough

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

•
Connect to the Version Control system
•
Register an object
•
Check out and edit an object
•
Check in the object and request approval
* 
NOTE: GPOADmin provides roles that enable users to perform actions within the Version Control system. The following scenario is created on the assumption that the administrator has already delegated the User and Moderator roles to the required users.

To view the roles applied to a specific container, right-click it, select Properties, and click the Security tab.

For complete information on how to create and delegate roles, see “Configuring Role-based Delegation” in the Quest GPOADmin User Guide or Online Help.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating