Chat now with support
Chat mit Support

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

Checking out objects

Before users can edit registered objects, they must be checked out. The workflow is as follows: Check-out the object from the system, make the required edits, and check in the changes to the system.

Checking out an object for the first time creates a copy of the original live version.

Version information is updated in the system’s history when the object is checked back in. Only one person within the system can check out and work on any object at a given time.

1
Expand the Version Control Root node and the required container.
1

Requesting the deletion of an object

Users can propose the deletion of objects in the enterprise environment that are currently registered in the Version Control system and in the Available state. If the request is approved, the object will be removed from the system and deleted from the live environment.

NOTE:  
1
Expand the Version Control Root node and the required container.

Unregistering GPOs and removing history

You can select to permanently unregister a GPO and remove any associated metadata from the configuration store.

1
Expand the Version Control Root node and the required container.
2
Right-click the required object and select Unregister and remove history.

Requesting approval

Once an object has been altered and checked in to the system, the update is ready to go through the approval process. (For more information on checking in objects, see Checking in controlled objects .)

1
Expand the Version Control Root node and the required container.
1
Select the altered GPO and click Workflow | Request Approval.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen