立即与支持人员聊天
与支持团队交流

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

Creating a report

You can create reports that show the details of controlled objects, as well as diagnostic and troubleshooting information. For more information on the available reports, see Creating Reports .

Working with available objects

With available objects, you can perform all the supported tasks of registered objects (Show history, view live reports, view properties, unregister, create labels, and import/export), as well as:

Enabling/disabling workflow

If you have the Enable/Disable right, you can enable and disable the workflow for a deployed object. The object must be under version control and be a major version (for example, 2.0).

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

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
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级