Chat now with support
Chat with Support

GPOADmin 5.16 - 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 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

Working with the live environment

•
Registering objects
•
Registered status
•
Removing registered objects
•
Viewing the live environment

Registering objects

Registering objects

To start working with the Version Control system, the GPOs, starter GPOs, scripts, DSC scripts, WMI filters, and Scopes of Management (Sites, Domains, and Organizational Units) must be registered. You have the option to make GPOs workflow enabled at the time of registration and to maintain the version history of objects that were previously registered within GPOADmin.

Registering and unregistering are recursive for objects when they are selected from the treeview on the left of the console. All child objects are included unless you individually select lower-level objects to register.

You have the choice of registering all items in the selected container or domain, all GPOs, all scripts, all DSC scripts, or all WMI Filters when you use the Register menu. When you register objects at the domain level, you do not automatically register GPOs, scripts, DSC scripts, or WMI filters in the domain unless they are already linked to the Scopes of Management that are being registered. You can select WMI Filters, scripts, DSC scripts, and GPOs separately, using their respective folders.

* 
NOTE: Only users with the Register and Unregister rights can register and unregister objects. For more information, see Configuring role-based delegation .
* 
NOTE: Scripts contained in the SYSVOLS Scripts folder (and its subfolders) can be registered and will be detected by the Watcher Service and reported as non-compliant. DSC scripts are not monitored by the Watcher Service.

When an object is added to the system for the first time, it will be automatically backed up (stored) in the Version Control system history and labeled with a version of 1.0, unless another major version number is specified during the registration process. Each time a change is made (an object is checked in) a minor number is added. For example, v1.2, v1.3, and v1.4. When a change is deployed to the enterprise by a user with the appropriate role, the version number will change to the next major number, for example, v2.0 and v3.0.

* 
NOTE: GPOADmin works with pre-existing GPOs, scripts, DSC scripts, WMI filters, and Scopes of Management, as well as any other objects created from within the system.
NOTE: If an object is not registered in version control, the modified date displayed is returned from the live object.
* 
NOTE: You must have the Register right and access to the Live Environment to perform the following steps.
* 
NOTE: Before you can register DSC scripts, you must enable DSC support in the Server options and specify a DSC root directory for each domain that will support DSC scripts. This root directory serves as the starting point for the DSC script enumeration and deployment location. See Editing the Version Control server properties .
* 
NOTE: The Starter GPOs folder is not created by default. To create the Starter GPOs folder, open Group Policy Manager, expand the required Domain | Starter GPOs, and click Create Starter GPOs Folder.|
To register objects using the GPOADmin console
1
Expand GPOADmin, the Live Environment, and domain nodes, and select the object you want to register within the Version Control system.
2
Right-click and select one of the following: Register - This Object Only, - All, - Group Policy Objects, - Scopes of Management, or - WMI Filters.
3
Select the container in which you want to place the registered object, or create a new container, and click OK.
Once the objects have been registered, they are located in the selected container under the Version Control Root with the initial version number set to 1.0. They are now available to be checked out and edited. You can set the major version number to any number greater than 1.0 (for example to maintain a version number if you are migrating from another Version Control system).
Users with the delegated rights can link registered GPOs to Scopes of Management (Sites, Domains, and Organizational Units) and add WMI Filters. For more information about linking GPOs, see Linking GPOs . For information about adding WMI Filters, see Creating Group Policy Objects (GPOs) .
To register GPOs using the GPMC Extension
* 
NOTE: You must use the GPOADmin console to register WMI filters and Scopes of Management.

Registering GPOs using the GPMC Extension is not recursive. If you want to register all child objects at once, use the GPOADmin console.

1
Expand the forest, domains, and domain nodes. Click the Group Policy Objects node, and select the GPO you want to register within the Version Control system.
2
Click Register.
3
Select the container in which you want to place the registered object and click OK.
OR
Click New Container and name the container then click OK.

Registered status

Registered status

You can quickly see the status of registered GPOs, starter GPOs, scripts, DSC scripts, WMI filters, sites, domains, and OUs. The objects will either be available for check out, already checked out, or checked in and awaiting approval to be committed to the enterprise. The options available to you at each state will depend on your specific role and permission. Registered objects will be in one of the following states:

 

Table 11. Registered Status
Status
From this state, depending on your assigned role and enabled options, you may have the ability to:

Available
•
link
•
search and replace
•
edit
•
check out
•
import and export settings
•
import Security Compliance Manager Backup in group policies
•
request approval (for objects that have minor versions greater than zero)
•
deploy (for objects that have minor versions greater than zero)
•
label
•
cloak/uncloak GPOs
•
lock/unlock GPOs
•
enable/disable workflow for GPOs, SOMs, and WMI Filters
•
managed by
•
check compliance
•
unregister objects
•
protected setting - export
•
create and save reports dealing with latest, and live objects, and the difference between them
•
show history
•
Synchronize – Synchronize Now and Set Synchronization Targets
•
edit object properties
•
refresh the object
•
cut
•
copy
•
mark objects for deletion
•
rename (This does not apply to SOMs.)

 

Table 12. Registered Status
Status
From this state, depending on your assigned role and enabled options, you may have the ability to:

Checked Out
•
link
•
search and replace
•
edit objects
•
check in objects
•
undo any check out
•
import and export settings
•
import Security Compliance Manager Backup in group policies
•
request approval (for objects that have minor versions greater than zero)
•
deploy (for objects that have minor versions greater than zero)
•
label
•
managed by
•
protected setting - export and verify
•
create and save reports dealing with latest, live, and working copy objects, and the difference between them
•
show history
•
Synchronize – Synchronize Now and Set Synchronization Targets
•
edit object properties
•
refresh the object
•
cut
•
copy
•
rename (This does not apply to SOMs.)

Pending Approval
•
link
•
search and replace
•
export settings
•
withdraw approval request
•
approve changes
•
reject
•
deploy the changes to the environment
•
label
•
managed by
•
protected setting - export
•
create and save reports dealing with latest and live objects, and the difference between them
•
show history
•
Synchronize –Set Synchronization Targets
•
edit object properties
•
refresh the object
•
cut
•
copy

Pending Deployment
•
link
•
search and replace
•
export settings
•
reject
•
withdraw approval
•
deploy the changes to the environment
•
label
•
managed by
•
protected setting - export
•
create and save reports dealing with latest, and live objects, and the difference between them
•
show history
•
Synchronize –Set Synchronization Targets
•
edit object properties
•
refresh the object
•
cut
•
copy

Removing registered objects

If you no longer want the object to be available for changes, you can remove it from the Version Control system, as long as you have been granted the Unregister right. Unregistering version-controlled objects is now recursive, unless you select the lower-level objects individually.

To remove objects from the Version Control system using the GPOADmin console
1
Expand the Version Control Root node and the required container.
2
Right-click the object and select Unregister.
To remove GPOs from the Version Control system using the GPMC Extension

Unregistering GPOs using the GPMC Extension is not recursive. If you want to unregister all child objects, use the GPOADmin console.

1
Select the Group Policy Objects node and then select the GPO.
2
Click Register or right click and select Unregister.
* 
NOTE: You can view a list of Unregistered objects in the Search Folders in the GPOADmin console. This includes GPOs, scripts, DSC scripts, WMI filters, and SOMs.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating