Chatta subito con l'assistenza
Chat con il supporto

GPOADmin 5.17 - 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 when users can modify objects 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

Undoing a check out

The user who checked out an object has the option of undoing the check out and reverting the state back to Available.

1
Expand the Version Control Root node and the required container.
1
Select the checked out GPO and click Workflow | Undo Check Out.

Checking in controlled objects

Once you have checked out an object and edited its settings (for more information, see Editing objects ), you have the option to:

A check in updates the history of the object within the Version Control system with the changes made while it was checked out. Included with any check-in is a comment and a unique minor version number (such as 1.1).

A check in does not allow the offline changes to go live into the enterprise environment as it must first be approved. Once an object is marked as Pending Approval, it cannot be checked out by any other user of the system.

Multiple check in and check outs are allowed to occur within the system without requiring approval. When a user checks in an object so it is available to another system user, the next user to check out the same object will be working with the current offline version consisting of all changes made to date. After all the users have made their required changes to the offline object it is processed by the approval system to determine if the changes are accepted to go live into the enterprise or not.

1
Expand the Version Control Root node and the required container.
4
Right-click and select Request Approval if required. Enter a comment and click OK.
1
Select the GPO and click Workflow | Check In.
3
Click Workflow | Request Approval if required. Enter a comment and click OK.

Working with objects pending approval and deployment

Only users with the Deploy permission can make the changes go live in the enterprise. The approval system safeguards the enterprise environment from any unauthorized live changes that could cause unwanted results. For more information on delegating permissions, see Configuring role-based delegation.

The types of requests from users that require approval are

For more information, see:

Withdrawing an approval request

Any user who proposes a change to an object can withdraw their own request for approval while the change is in the Pending Approval state.

2
1
Select a GPO in the Pending Approval state, and click Workflow | Withdraw Approval Request.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione