Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Creating scripts

Logon, logoff, Startup and Shutdown 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.

Users with the appropriate permission can propose the creation of a script that does not currently exist in the enterprise environment and have it placed within the Version Control system.

To propose the creation of a script:
1
Right-click the Version Control container and select New | Script.
2
Enter a descriptive name and domain where the script will be used.
3
Select where you want to deploy the script and click Finish.

Creating Desired State Configuration (DSC) PowerShell scripts

Desired State Configuration (DSC) extends Microsoft PowerShell to facilitate environment configuration – including your GPO deployment. Users with the appropriate permission can propose the creation of a script that does not currently exist in the enterprise environment and have it placed within the Version Control system.

* 
NOTE: Only DSC PowerShell scripts are supported.
To propose the creation of a DSC PowerShell script:
1
Right-click the Version Control container and select New |DSC Script.
2
Enter a descriptive name and domain where the script will be used.
3
Select where you want to deploy the script and click Finish.

Merging GPOs

To reduce complexity and limit the number of GPOs in your organization, you can select to merge the settings of two GPOs into a single GPO or create a new GPO based on the merged settings. During the merge, any conflicts will be identified so that you can address them as required.

* 
NOTE: Required Permissions
•
To create a new GPO based on two existing GPOs:
•
Read, Create and Edit permissions
•
Read and Create Group Policy Object domain rights
•
To merge GPO settings into an existing GPO:
•
Read and Edit permissions
•
Read domain right
To merge GPO settings into a new GPO
1
Expand the Version Control Root node, and select two GPOs.
2
Right-click and select Merge | Merge To New Group Policy Object.
If conflicting settings are identified, the Merge Conflict Resolution dialog opens. To resolve the conflict, select the settings that you want applied. Once all conflicts are resolved click OK.
3
In the New Group Policy Object Wizard, enter a name and select the location for the GPO and click Next.
4
If required, select the WMI Filter to associate with the GPO and click Finish.
The new GPO will be created based on the settings of the merged GPOs.
To merge settings into an existing GPO
1
Expand the Version Control Root node, and select two GPOs.
2
Right-click and select Merge | Merge To Existing Group Policy Object.
If conflicting settings are identified, the Merge Conflict Resolution dialog opens. To resolve the conflict, select the settings that you want applied. Once all conflicts are resolved click OK.
3
Select the target GPO for the merged settings and click OK.
The target GPO will now have the settings from both of the selected GPOs.
4
You now have the option to replace the Scope of Management links in the source GPO with the links in the target GPO. Click Yes, to replace the links, and Yes again in the Search and Replace Links wizard to complete the process.
* 
NOTE: This option is only available if the source GPO is currently liked to a SOM, the source and target GPO are in the same domain, and the user performing the merge has the Link right on the target GPO.

Restoring an object to a previous version

You can easily create a report that displays the historical settings for objects in the Version Control system or a comparison of versions to locate the differences. For more information, see Establishing Management for an Object and Creating Reports .

You can also import settings from any version in the history of the Version Control System, as well as links between Group Policy Objects and Scopes of Management. This effectively creates a roll back to an earlier set of parameters. You must have the object checked out to perform this action. You must also have the Link right to restore links. For more information, see Configuring role-based delegation .

Rolling back to a particular version of a workflow enabled GPO does not affect the live enterprise environment until it has gone through the complete approval process. For a workflow disabled GPO, the effect is immediate.

From this point forward, the basic workflow of GPOADmin takes over once again. You must check in and approve the changes to have them go live in the enterprise environment.

For information about restoring inks, see Restoring links to a previous version .

To restore a previous version of an object using the GPOADmin console
1
Expand the Version Control Root node and select the required container.
2
In the right pane, select the required object, right-click and select Show History.
You will see the name, type, version, action, account, date and comment pertaining to the history item.
3
Select the filtering options you want to apply.
4
To view the settings of a previous version, right-click the specific version you want, and click View.
To view the difference in settings between two versions, select the versions using Ctrl + select, then right-click and click Differences.
5
Right-click the specific version you want to restore and click Get.
* 
NOTE: When you Get a previous version of a workflow disabled GPO, the major version number will be increased by one.

The Get command replaces the settings in the working copy with those from the selected version. If the current object is not checked out, then the Get command will automatically perform a checkout, provided you have the required Edit right. If you do not have the Edit right then the Get option will not be available.

If you are rolling back the links of a GPO whose domain is different to that of the SOM to which it is linked, that SOM would not be available in the dialog box for management.
6
Enter a comment if required.
You can choose to restore GPO Links. For more information, see Restoring links to a previous version .
7
Click OK.
8
Click Close.
To restore a previous version of a GPO using the GPMC Extension
1
Select the GPO and click Show History.
The history displays in the bottom pane of the GPO Management tab. You will see the name, version, action, account, date and comment pertaining to the history item.
2
To view the settings of a previous version, select the version, right-click it and select View.
To view the difference in settings between two versions, select the versions using Ctrl + select, then right-click and click Differences.
3
Right-click the version you want to restore and click Get.
* 
NOTE: When you Get a previous version of a workflow disabled GPO, the major version number will be increased by one.

The Get command replaces the settings in the working copy with those from the selected version. If the current object is not checked out, then the Get command will automatically perform a checkout, provided you have the required Edit right. If you do not have the Edit right then the Get option will not be available.
4
Enter a comment if required.
You can choose to restore GPO Links. For more information, see Restoring links to a previous version .
5
Click OK.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation