Chat now with support
Chat with Support

GPOADmin 5.18 - 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)
Creating a custom container hierarchy Selecting security, levels of approval, and notification options Viewing the differences between objects Copying/pasting objects Proposing the creation of controlled objects Merging GPOs Restoring an object to a previous version Restoring links to a previous version Managing your links with search and replace Linking GPOs to multiple Scopes of Management Managing compliance issues automatically with remediation rules Validating GPOs Managing GPO revisions with lineage Setting the change window for specific actions Working with registered objects Working with available objects Working with checked out objects Working with objects pending approval and deployment
Checking compliance Editing objects Synchronizing GPOs Exporting and importing
Creating Reports 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

Appendix: GPOADmin Backup and Recovery Procedures

•
GPOADmin Backup Requirements
•
Restoring GPOADmin

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:

•
The GPOADmin configuration store.
•
The GPO backups store.

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.

* 
NOTE: While GPOADmin is inaccessible, you can manage GPOs through the Group Policy Management Console (GPMC).

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.

To restore the ADLDS instance
•
For information on how to backup Microsoft AD LDS see: https://technet.microsoft.com/en-us/library/cc794761(v=ws.10).aspx or Microsoft TechNet.
To restore the file share
•
Follow your internal procedure for recovering files and folders.
If you plan to use a new host computer for the GPOADmin backup store, or the host computer has been renamed, please contact Quest Customer Support for assistance.

 

Appendix: Customizing your workflow

•
What is a custom workflow action?
•
Working with custom workflow actions in the Version Control system
•
Working with the custom workflow actions xml file
•
Troubleshooting custom workflow actions
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating