GPOADmin 5.17 - User Guide


	NOTE: To protect your environment from a SQL Injection attack, you can mark which SQL statement inputs are not permitted. See Editing the Version Control server properties. By default, all of the inputs are marked as not permitted. If you allow these inputs, malicious code may be inserted in a SQL statement resulting in security vulnerabilities.

To connect as the current user, select NT Authentication.

To connect using SQL credentials, select SQL Authentication and enter the user name and password.

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

Right-click the forest, and select Copy Server Configuration.

Select the server configuration that you want to copy and click OK.

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

Migrating from AD/AD LDS to a SQL configuration store

A configuration utility (GPOADmin.ConfigMig.exe) is available in the GPOADmin install directory 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.

NOTE:

•

The Migration utility migrates configuration store data; it does not migrate backups. To ensure the migration completes without issue, we recommend that you continue to use the same backup store.

•

To ensure the configuration utility is running against the latest version of GPOADmin, login and configure for the existing AD/AD LDS configuration store prior to migrating to SQL. This also ensures that AD/AD LDS configuration store is up-to-date and reduces possible migration issues.

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 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 above configuration storage location.

•

After the migration, you need to restart the Watcher Service so that it will use the correct configuration store.

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 configuration store to change the storage from AD/AD LDS to SQL.

SQL Injection inserts malicious code into SQL statements which can lead to security vulnerabilities. To protect your environment from a SQL Injection attack, you can mark SQL statement inputs that are not permitted. See Editing the Version Control server properties. By default, we have marked the following inputs as not permitted. If you allow these inputs, malicious code may be inserted in a SQL statement resulting in security vulnerabilities:

Table 8. SQL inputs
Input	Description
:	Denotes the end of a SQL query. Allowing this character can permit malicious queries to be included in user input.
--	All trailing input is interpreted as a comment until the new line character.
/*	The character combination used to denote the start of a block comment. All trailing input is interpreted as a comment until the comment end delimiter.
*/	The character combination used to denote the end of a block comment. Input between the comment start delimiter and the comment end delimiter is interpreted as a comment.
xp_	Extended procedures are routines residing in DLLs that function similarly to regular stored procedures. The extended stored procedure function is run under the security context of Microsoft SQL Server.
\AUX	Generally, the AUX port on a PC is computer port 1 (COM1), which is the first serial port with a preconfigured assignment for serial devices. File paths can be constructed using this input.
\CLOCK$	The system clock. File paths can be constructed using this input.
\COM1	The first Communications port. File paths can be constructed using this input.
\COM2	The second Communications port. File paths can be constructed using this input.
\COM3	The third Communications port. File paths can be constructed using this input.
\COM4	The forth Communications port. File paths can be constructed using this input.
\COM5	The fifth Communications port. File paths can be constructed using this input.
\COM6	The sixth Communications port. File paths can be constructed using this input.
\COM7	The seventh Communications port. File paths can be constructed using this input.
\COM8	The eighth Communications port. File paths can be constructed using this input.
\CON	A common device name for the keyboard and screen. File paths can be constructed using this input.
\CONFIG$	A configuration information file. File paths can be constructed using this input.
\LPT1	The first line print terminal. File paths can be constructed using this input.
\LPT2	The second line print terminal. File paths can be constructed using this input.
\LPT3	The third line print terminal. File paths can be constructed using this input.
\LPT4	The fourth line print terminal. File paths can be constructed using this input.
\LPT5	The fifth line print terminal. File paths can be constructed using this input.
\LPT6	The sixth line print terminal. File paths can be constructed using this input.
\LPT7	The seventh line print terminal. File paths can be constructed using this input.
\LPT8	The eighth line print terminal. File paths can be constructed using this input.
\NUL	The NUL port. File paths can be constructed using this input.
\PRN	The DOS name for the first connected parallel port. File paths can be constructed using this input.