Chat now with support
Chat with Support

We are currently preforming website maintenance, any feature requiring sign-in is temporarily unavailable, if you have an issue requiring immediate assistance please call Technical Support.

GPOADmin 5.13.5 - 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 About Us

Create a Protected Settings policy

Once the ability to use Protected Settings has been enabled, you can create the policies using one of the following methods:

Select the Protected Settings container in the tree view.
Right-click and select New | New Protected Settings Policy.
Click Finish.
Refresh the Protected Settings container.
In the Version Control Root, select the GPO you want to use for a Protected Settings policy.
Refresh the Protected Settings container.

Protecting policy settings based on extensions

If required, you can prevent users from editing policy settings based on one or more policy extensions. Once you have selected the extension to block, if a policy contains any settings from the extension, the policy will fail the validation test and will not be checked in.

Available extensions include:

Select the Protected Settings tab and the Blocked Extensions tab.

Generating Protected Settings policies reports

The following reports are available for Protected Settings policies: Latest, Working Copy, and Differences reports.

Select the Protected Settings Root container in the tree view.

Using Protected Settings policies

Once Protected Settings policies have been enabled through the Version Control properties and created they need to be applied to a container in GPOADmin.

This is done through new option on all containers that becomes available when the Enable Protected Settings for Group Policy Object is enabled.

Select the Protected Settings tab.
Select the Add button.
Settings defined in the Protected Settings policy are not allowed: If a setting with the same name as a setting in the protected policy is detected in an active GPO, notification is generated. The value does not have to be the same for the setting, just the setting name.
Values other than those defined in the Protected Settings policy are not allowed: If there is a setting used in the active GPO that has a value different than the protected value, then a notification is generated.
To block the Protected Settings from the parent container, select the Block Protected Settings Inheritance setting. You may want to do this as this container needs a unique protected setting and the setting from the parent would conflict with the new settings being applied.
If necessary, select Include Group Policy Objects in all child containers to allow the checking of all child containers against the assigned protected settings policy.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating