Chat now with support
Chat with Support

GPOADmin 5.15 - User Guide

Introducing Quest GPOADmin Configuring GPOADmin Using GPOADmin
Connecting to the Version Control system Navigating the GPOADmin console Search folders Accessing the GPMC extension Configuring user preferences Working with the live environment Working with controlled objects (version control root) Checking compliance Editing objects Synchronizing GPOs Exporting and importing
Creating Reports Working with the GPOADmin Dashboard Appendix: Windows PowerShell Commands Appendix: GPOADmin Event Log Appendix: GPOADmin Backup and Recovery Procedures Appendix: Customizing your workflow Appendix: GPOADmin Silent Installation Commands Appendix: Configuring Gmail for Notifications Appendix: Registering GPOADmin for Office 365 Exchange Online Appendix: GPOADmin with SQL Replication About Us

GPOADmin Backup Requirements

As part of your normal disaster procedures or requirements, GPOADmin should be considered for inclusion. In the event of a computer or network failure, the GPOADmin deployment and its data can be restored if you have performed regular and distributed backups of the following:

During the initial installation of GPOADmin, you must specify where to place these two items within your environment. The configuration store can reside in either Active Directory or AD LDS. The GPO backup store can be in Active Directory, AD LDS, a network share, or on a SQL server. The recommended location is on a network share.

Each of these options has its own backup strategies and requirements and should be included in your regular backup schedule.

Restoring GPOADmin

Once you have performed the required recovery procedures listed below, simply reinstall GPOADmin, configure the services to use the recovered stores and resume the management of GPOs. For configuration details, see Configuring the Version Control server .

Any policies that were checked out, checked in, or pending approval up to the time of the last backup will be not be affected by the failure.

For information on how to backup Microsoft AD LDS see: or Microsoft TechNet.


Appendix: Customizing your workflow

What is a custom workflow action?

You can extend GPOADmin’s version control system to incorporate customized actions based on your organizations existing workflow. This allows you to customize and control the deployment of controlled objects (such as GPOS, SOMs, and WMI filters) to meet your individual needs. For example, you can configure a pre-action to send the help desk distribution list an email each time a GPO change is requested.

Also, if you have a workflow tool in place that encompasses many different organizational tools you no longer need to use the workflow in both applications. With pre and post actions, a GPO check out, modification, and request for approval can be configured to create a ticket in an existing workflow system. Subsequent approval in the external workflow system can be configured to approve and deploy that same policy in GPOADmin. A post action can be configured to add additional ticket information about the deployment of the GPO into the customers external workflow application.

Custom actions are available on the following Version Control actions:


A change to a version controlled object is approved.


A version controlled object’s scheduled deployment has been canceled.


A version controlled object is checked in.


A version controlled object is checked out.


A version controlled object has been cloaked.


Either a “Rollback” or “IncoporateLive“ compliance action is performed.


A version controlled object has been created.


A version controlled object has been deleted.


A version controlled object has been deployed into the live environment.


A version controlled object has been workflow disabled.


A version controlled object has been modified.


A version controlled object has been workflow enabled.


A label has been applied to one or more version controlled objects.


A version controlled object has been locked.


The security has been modified on a version controlled object.


A version controlled object is moved.


An object is registered with the version control system.


A change to a version controlled object is rejected.


A version controlled object is renamed.


An approval for a version controlled object is requested.


A version controlled object has been restored.


A version controlled object has been scheduled for deployment.


A version controlled Group Policy Object has been synchronized with another Group Policy Object.


Toggles a version controlled object between workflow enabled and disabled.


A version controlled object has been uncloaked.


A version controlled object’s checkout is undone.


A version controlled object has been unlocked.


A version controlled object is unregistered.


An approval on a version controlled object is withdrawn.


A request for approval has been withdrawn.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating