GPOADmin 5.17 - User Guide

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.

To apply a Protected Settings policy

Right-click a container and select Properties.

Select the Protected Settings tab.

Select the Add button.

Select the policy to apply and click OK.

The selected protected policy displays in the Assigned Protected Settings policy window with the default validation rule.


	NOTE: Inherited policies are displayed as disabled.

Select the validation rule that will be used to detect if a user is attempting to use or alter a protected setting, and choose to base it on Settings or a Value.

If you selected Value from the drop-down list, you can now choose the items to check. Select from the following:

None: Items that exist in the policy that do not exist in the Protected Settings Policy are ignored.

User Rights Assignment: Items that exist under the User Rights Assignment in the policy that do not exist in the Protected Settings Policy are included in the validation process and are flagged as Invalid.

All: Items that exist in the policy that do not exist in the Protected Settings Policy are included in the validation process and are flagged as Invalid

A check is made for any similarities between the Protected Settings policy and the GPO being checked in. This can be either based on the settings name or value.

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.

Exclusions can be set for any GPO in the container which may contain protected settings. This allows specific GPOs to be excluded from any protected setting checking. Place a tick in the check box for any of the listed GPOs that you want to exclude from the Protected Settings policy.

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.


	NOTE: Because there can be GPOs with the same name in GPOADmin, the path of the GPO is also listed to ensure that you select the correct GPO for exclusion.

Once you are satisfied with your selections, click Apply and then OK.

Checking a GPO against a Protected Settings policies and blocked extensions

A GPO that resides in a container with Protected Settings enabled will be checked against the protected settings policy when the GPO is checked in using Check-In.

During a check-in, the GPO is checked against the Protected Settings policy and any blocked extensions. Users that have the Modify Protected Settings right on the GPO in question, will have the option to continue with the check in and override the blocked setting or review a report and address the issue.

The report displays with the associated Protected Settings policies and blocked extensions, how many matches were found, and the Validation mode (either setting name or value).


	NOTE: The GPO remains checked out until the issue with the Protected Settings policy is rectified and the GPO passes the check.

Validating a GPO against a Protected Settings policies and blocked extensions before a check-in

A GPO can be checked against the Protected Setting policy and blocked extensions before checking it in.

To check a GPO before a check-in

Right-click the GPO you want to check and select Protected Settings | Verify Protected Settings.

This checks the GPO against the Protected Settings policy and blocked setting. If the GPO includes secured settings, a dialog box displays with the associated Protected Settings policies, blocked extensions, how many matches were found, and the Validation mode (either setting name or value).

Select View Report to generate a report that displays the differences between the GPO and the Protected Settings policy. You can select to print or save the report. Once you have finished viewing the report click Close.

Click OK in the Protected Settings Modifications Detected dialog box to close it.