GPOADmin 5.20 - Quick Start Guide

Select Users and add/remove users who can connect to the Version Control server, but can only perform those actions that have been assigned by an administrator.

Select Storage to select the location of the physical backup copy of the various versions of an object.

You can choose between:

Backup store location: This will store the backups in Active Directory if you selected it during the initial setup of GPOADmin as the storage method for your configuration.


	NOTE: Active Directory is not recommended for production deployments due to the amount of replication data.

AD LDS: This will store the backups in Active Directory Lightweight Directory Services (AD LDS).

Enter the server name and port.


	NOTE: To use the same AD LDS instance for both the configuration and backup store, select the “Configuration store location” option on the Backup location page.

Network Share: Enter or browse to a network share or directory.


	NOTE: This is the recommended method as it provides a high level of performance and a low level of configuration and maintenance overhead.

SQL Server: This will store the backups in SQL Server. Enter the database name and the required authentication.


	NOTE: If the server is installed as a unique instance, it must be specified as servername\instancename rather than just the SQL Server name.

To help optimize performance and secure your data by configuring accepted SQL input filters and timeout settings, select SQL.

To protect your environment from a SQL Injection attack, choose the SQL Input Filters option to specify which SQL statement inputs are not permitted within your deployment. 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 vulnerability.

Choose the SQL Timeouts option to configure how long GPOADmin will wait to connect to the SQL server or to process a command.

Adjust the timeout values that best fit your deployment and click OK.

The default for the connection timeout is 15 seconds and the default for the command timeout is 30 seconds.

Select Desired State Configuration | Root directory to specify a DSC root directory for each domain that supports DSC scripts. This root directory serves as the starting point for the DSC script enumeration and deployment location. DSC scripts cannot be registered until this option is enabled.

Select Scripts to set the file types that will be returned when enumerating Scripts in the live environment. Add and remove the file extensions as required and click OK.

Select Delegation | Roles to create and edit roles that will be used to delegate rights over the Version Control system.

The built in roles and descriptions are displayed. Add, edit, and delete roles as required.


	NOTE: You cannot alter predefined roles.

For complete information on creating and delegating roles, see Configuring role-based delegation in the User Guide.

Select Notifications to configure email notifications on Version Controlled events. Notifications help you to stay informed of the latest changes to objects under version control and can be enabled for Exchange on-premises, Office 365 Exchange Online, and Gmail.

To use notifications, you must enable SMTP and set the method of authentication. The required method is dependent on the mechanism selected to send notifications.

•

When using Exchange on-premises, basic authentication is required.

•

When using Office 365 Exchange Online, OAuth 2.0 authentication is required.

•

When using Gmail a credential file is required.

Table 3. SMTP options

Option

Procedure

Select SMTP to modify the global SMTP notification options.

NOTE:

•

Users can alter the email address for their notification email through their personal settings, or through the Notification Manager. See the User Guide for details.)

•

GPOADmin supports TLS/SSL connections. When connecting to Office 365 for standard SMTP notifications, the From account must be a valid email address and have access to the mailbox of the authentication account.

•

To ensure secure communication between GPOADmin and your Exchange server, it is recommended that your Exchange server be configured to support TLS 1.2.

•

If you select to use Gmail, a folder directory is created in the location of the credential file which contains a tokens.json response folder and a corresponding token response file. This file is no longer required once the activation has been processed and can be safely removed.

•

If you want to use Microsoft Azure GCC High email for notifications, select the U.S Government GCC High option. For information on using Exchange Online for US Government environments refer to Microsoft documentation.

Select Basic to use Exchange for notifications.

Select to Enabled SMTP notifications.

Enter the SMTP server.

Enter the port number. 25 for standard, unencrypted communication, 465 for older SSL communication, or 587 for TLS communications.

Enter a “From” address. If your SMTP server is not configured for anonymous connections, enter the associated credentials.

You can optionally select to attach read and/or delivery receipts with notifications. Once enabled, the email specified in the “From” address can confirm that notifications are received and/or read after they are sent.

Select Exchange Online to use Office 365 Exchange Online for notifications.

Select to Enabled SMTP notifications via Exchange.

Enter the application ID, tenant ID, tenant name, certificate, certificate password, and https://outlook.office365.com/ews/exchange.asmx as the Exchange Server Url.

The application ID, tenant ID, tenant name, certificate, and certificate password are set when you register GPOADmin to use Office 365 Exchange Online through Microsoft Entra. See the User Guide appendix Registering GPOADmin for Office 365 Exchange Online for details.

Select Gmail to use Google mail for notifications.

Select to Enabled SMTP notifications via Gmail.

Enter the Gmail account.

Enter the credential file location. (To use Gmail, users must generate this credentials file from Gmail. GPOADmin uses this file to connect to Gmail, verify the authorization, get access and refresh tokens to retrieve and send messages.) See the User Guide appendix Configuring Gmail for Notifications for information on creating this file.

To navigate past the application verification warning, click Advanced and then click the Go to GPOAdmin (unsafe) link.

Grant GPOAdmin permissions to View and modify but not delete your email.

Click Allow to confirm your selection.

Table 4. Workflow notification options

Option

Procedure

Select Workflow to enable workflow approval through email, set the authentication method, and modify the mailbox and server information.

NOTE:

•

The Exchange option supports at a minimum Microsoft Exchange 2010 for on-premises mailboxes and Office 365 Exchange Online.

•

All approvers and the service account must have a valid Exchange on-premises or Office 365 Exchange Online inbox.

•

Distribution lists should be used for approval groups.

•

Proper Exchange certificates must be installed on the GPOADmin server if certificates are being used in your Exchange environment.

•

You must restart the GPOADmin service when you enable or disable this option.

•

If you want to use Microsoft Azure GCC High email for approvals, select the U.S Government GCC High option. For information on using Exchange Online for US Government environments refer to Microsoft documentation. This option is only available for OAuth 2.0 Authentication.

Select Exchange to use Exchange or Exchange Online for notifications.

Select Enable Workflow Approval through email.

Set the required authentication.

To use Exchange for notifications, select Basic and enter the account to use to connect to the mailbox and password. Enter the Exchange Server Url or select Autodiscover Exchange Server Url to locate the Exchange server that is hosting the specified mailbox.

By default, GPOADmin uses the mailbox associated with the service account. If necessary, you can specify a different mailbox for the service to use when processing approvals and rejections through email. To do so, uncheck the Use the service accounts mailbox option and enter the mailbox that you want to the service to monitor. To connect as the service, leave the account blank and password blank.

To use Office 365 Exchange Online for notifications, select Exchange Online. Enter the mailbox application ID, tenant ID, tenant name, certificate, certificate password, and https://outlook.office365.com/ews/exchange.asmx as the Exchange Server Url.

(The application ID, tenant ID, tenant name, certificate, and certificate password are set when you register GPOADmin to use Office 365 Exchange Online through Microsoft Entra. See the User Guide Appendix: Registering GPOADmin for Office 365 Exchange Online for details.)

Select Gmail to use Google mail for notifications.

Select to Enabled SMTP notifications via Gmail.

Enter the Gmail account.

Enter the credential file location. (To use Gmail, users must generate this credentials file from Gmail. GPOADmin uses this file to connect to Gmail, verify the authorization, get access and refresh tokens to retrieve and send messages.) See the User Guide Appendix: Configuring Gmail for Notifications for information on creating this file.

To navigate past the application verification warning, click Advanced and then click the Go to GPOAdmin (unsafe) link.

Grant GPOAdmin permissions to View and modify but not delete your email.

Click Allow to confirm your selection.

Select Logging | Configuration to enter the log location and the type of information you want to track.

You can choose to log to the Event Log, to a specific directory where log files will be created, or not at all.

You can also select which (if any) types of events to log. The types of events are as follows: Service Actions (such as service startup and shutdown), User Actions (such as check in, approve, edit), Errors, and Debug Information (used by Quest support personnel).

Select Options to configure various settings.

Select General to configure the following options:

Table 5. General options

Option

Description

Perform Group Policy Management version check

Check to ensure the version of GPMC on the client is compatible with the GPMC version used within GPOADmin.

Disable all workflow options for Group Policy Objects

Disable all workflow on GPOs.

Keep in mind, if you disable the workflow, any changes made are immediately deployed in the live environment. To bring the GPO back under version control, enable the workflow.

Disable all workflow options for Scopes of Management

Disable all workflow on SOMs.

Keep in mind, if you disable the workflow, any changes made are immediately deployed in the live environment. To bring the SOM back under version control, enable the workflow.

Disable all workflow options for WMI Filters

Disable all workflow on WMI filters.

Keep in mind, if you disable the workflow, any changes made are immediately deployed in the live environment. To bring the WMI filter back under version control, enable the workflow.

Set default link state to enable when adding new links

This enables the default link state for any new links added to a SOM.

Enable Protected Settings for Group Policy Objects

This enables the ability to have Protected Settings policies that contain settings that you want to control. They are protected in the sense that they contain and identify the settings that cannot be altered by users. This provides an added level of security for the policies within your organization. If a user attempts to create, edit, or remove the flagged settings they are stopped.

Enable Group Policy Object Synchronization

Synchronizing GPOs allows you to automatically push out predefined GPO settings to specified targets both within a forest and between two forests. This allows you to ensure specific GPOs, which are required in every domain, contain the same settings without having to link to a GPO outside of the domain.

You are able to select one or more GPOs from various domains as synchronization targets for the source GPO. When the source GPO has been successfully deployed, the settings from the last major backup are imported into each synchronization target GPO.

Allow the service account to synchronize Group Policy Objects during deployment

Provides the ability to control whether the service account can perform a GPO synchronization during deployment.

•

If disabled, a GPO synchronization will only happen during deployment if the deploying account has the Synchronization right on the GPO.

•

If enabled, the service account will perform a GPO synchronization during deployment. (Default)

Enable Unique Name

This ensures that GPOs and WMI filters cannot be created with the same name as an existing GPOs or WMI filter in a domain, select the Enforce Unique Names option. If a non-deployed GPO indicates that a duplicate name exists, run a full compliance check to determine if any GPOs were modified outside of GPOADmin.

Enable Unique Role Names

This ensures that roles cannot be created with the same name as an existing role.

Enable unregistered Scopes of Management linking

To allows users to link to unregistered Scopes of Management, select the Enable unregistered Scope of Management linking option. If this option is not selected, the policy and the SOM must be registered and the user linking the policy must have the Link right on both objects.

Display only the WMI Filters a user has Read access to when editing a GPO

Users are restricted to only the WMI Filters they have Read access.

Ensure service account access prior to deployment

This option must be enabled if you want users to be able to automatically deploy an object’s associated items.

It ensures that the service account has the Edit settings, delete, modify security rights on the working copy before deployment.

Enable the identification of associated items during deployment

Provides users with the option to identify and deploy associated items in a pending deployment state.

Prevent approval requester from approving their own changes

Ensures that a user cannot approve their own changes, even if they are in the approver's list for the object.

Enable the processing of custom workflow actions

Clicking the Launch Editor button starts the Custom Workflow Editor.

OU display format

Set the display format for OUs.

Select SQL Input Filters to view the allowed strings and characters for SQL statements.


	NOTE: To protect your environment from a SQL Injection attack, you can mark which SQL statement inputs are not permitted. If you allow these inputs, malicious code may be inserted in a SQL statement resulting in security vulnerabilities.

Select Comments to enforce comments to all actions and naming conventions for newly created objects. Set a minimum comment length greater than 0. Leaving the value at 0 means comments are optional for all actions. Any value greater than zero makes comments mandatory for all actions and all users.

Select Deployment Failure to enable an automatic retry on failed deployments. Enable the option and select the number of attempts (maximum of 10) and the interval in minutes (maximum of 1440). Re-deployment attempts are done as scheduled deployments.

Select Preferred Domain Controllers and click Add to configure the domain controller that GPOADmin will use for all Active Directory actions. By default, GPOADmin uses the Primary Domain Controller.

Select Backups Retention to configure a retention schedule for backups. You can select to limit the backups to keep based on a specified number, age, or date. Backup retention settings apply to SQL configuration stores only.


	NOTE: All backups generated by the watcher service due to non-compliance are counted in the retention limit.

Select License | Current License to view the current license information.

Select the Update License check box and then click Browse and go to the new license location.

Select Intune | Configuration to enable support for Intune and enter the information to connect to the required Microsoft Entra tenant. This includes the application ID, tenant ID, tenant name, certificate, and certificate password for the tenant where Intune is installed. See the Minimum permissions, rights, and roles required for Microsoft Intune.

Select Integration to configure settings that apply to a Quest Change Auditor™ integration.

If you have multiple Change Auditor coordinators installed, you can select a specific coordinator to use for reports and auditing.

If necessary, you can also select to turn off Change Auditor, by selecting Not Set.

Select Enable FIPS Mode. The Federal Information Processing Standards (FIPS) are government set guidelines and standards published by the National Institute of Standards and Technology. To run a Windows environment in FIPS compliant mode, the Microsoft Policy “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” must be enabled.

Select Enable FIPS mode to ensures that GPOADmin uses cryptographic algorithms that are FIPS compliant.

Select Allow self-signed certificates when communicating with Exchange servers if required.

Both these options are enabled by default.

When you have made all the required selections, click OK

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

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.

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.

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.

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.

If you select SQL Server, choose the required SQL server, enter a name for the database, select the authentication method to access the server.


	NOTE: See the Release Notes for supported SQL Server versions.

To connect as the current user, select NT Authentication.

Select the level of encryption for the connection. When enabled, SQL Server uses TLS encryption for data sent between the client and server.

Choose between:

•

Strict (SQL Server 2022 and Azure SQL): Select this option for Azure SQL Database and Azure SQL Managed Instance or when the instance has Force Strict Encryption enabled.

•

Mandatory (Default in GPOADmin): Select this option when the instance has Force Encryption enabled. It can also be used when no encryption is configured for the instance, but Trust server certificate is enabled. While this method is less secure than installing a trusted certificate, it does support an encrypted connection.

•

Optional

Enabling Trust Server Certificate, when 'Optional' or 'Mandatory' encryption is selected, or if the server enforces encryption, means that SQL Server will not validate the server certificate on the client computer when encryption is enabled for network communication between the client and server.

Under Host name in the certificate, you can provide an alternate, yet expected, Common Name (CN) or Subject Alternative Name (SAN) in the server certificate for the connection to SSMS. You would use this option when the server name does not match the CN or SAN, for example, when using DNS aliases.

Leaving this option blank allows certificate validation to confirm that the CN or SAN matches the server name.

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

Click Next to continue.

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 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.20 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.16 or later configuration storage location. (Upgrade from versions older than 5.16 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

•