サポートと今すぐチャット
サポートとのチャット

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

Connecting to the Version Control system

Connecting to the Version Control system

When the GPOADmin console is closed, the GPOADmin servers you were connected to are persisted, so the next time you open GPOADmin the connections to those servers are initiated automatically.

If you selected the “Remember my password” check box during the initial connection, then you will not be prompted for credentials the next time you connect. Each connection to this server from here on will automatically use the specified credentials, which are stored in Windows Credentials Manager. To logon as a different user, you must remove the entry from the Windows Credentials Manager.

To connect to the Version Control system using the GPOADmin console
1
Right-click the GPOADmin node and select Connect To.
2
Click New to create a new connection and enter the server name.
The connection dialog, is automatically populated with GPOADmin Services detected in the environment.
3
Select the required Version Control server and click Connect to connect with the current logged on user credentials or select the down arrow in the Connect button and select Connect As to enter new credentials (domain\user and password).
4
To save the credentials, select the Remember my password check box and click OK.

Restricting search scope

If required, you can restrict which global catalogs are used within the forest to search for the GPOADmin server during connection.

To restrict the search scope:
1
Create a file called PreferredGCs.txt.
2
List the fully qualified domain name of each Global Catalog server to include in the search on their own row in the file.
3
Save the file to the installation directory.

When you connect to GPOADmin, only the global catalog servers listed in the file will be searched as possible connection points. If this file is not included, GPOADmin will search all global catalog servers in the forest.

Working with multiple connections

If you have multiple connections, consider the following:

•
Each connection display its own Lost and Found, Report, and Search Folder containers.
•
When connecting to GPOADmin, the User Preferences menu option is disabled if you are not logged on to the client host computer. (This is because this option is stored in the registry of the connected user.)
•
When connecting to GPOADmin, you are prompted to select a report location when first accessing the Reports container if you are not logged on to the client host computer. (This is because the users report folder is stored in the profile of the connected user.)
•
If you connect to GPOADmin and have been assigned multiple root containers through group membership, you may have access to the same folders through each root container.
For example, you have a container called PARENT which has a child container called CHILD and you are a member of Group A and Group B. Group A is assigned PARENT as their root container; Group B is assigned CHILD as their root container. When you log into GPOADmin you will see both PARENT and CHILD as root containers instead of the Version Control Root container, allowing for two ways to access the CHILD container.

Version Control data in the directory

GPOADmin does not delete the information stored in the directory when it is uninstalled. The Version Control information may be deleted manually if it is no longer required.

GPOADmin uses "working copies" of objects for editing purposes. If the Version Control information is deleted from the server, while objects are still pending creation or in a minor version, these working copies may be seen as "Unregistered" if a new instance of the version control information is instantiated.

 
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択