Tchater maintenant avec le support
Tchattez avec un ingénieur du 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

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.

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).

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.

Right-click the GPO you want to check and select Protected Settings | Verify Protected Settings.
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.


Using GPOADmin

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation