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

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

GPMC Extension on another computer

This command installs the GPMC Extension on a computer that does not have GPOADmin components installed.

Silent install of GPMC Extension (specified server):
msiexec /quiet /l* Install.log /i "Quest gpoadmin" LICENSEACCEPTED=1 /q ADDLOCAL=GPMCExtensionFeature SERVERNAME="server_name"
* 
NOTE: The parameter "server_name" is the name of the computer where the GPOADmin service is installed.

Appendix: Configuring Gmail for Notifications

•
Using Gmail for Workflow Approvals
•
Creating a Gmail Credentials File

Using Gmail for Workflow Approvals

To enable the ability to approve or reject changes through Gmail, you need to:

•
Create a gmail account. This account is responsible for the application activities, settings, and API credentials. See https://www.google.com/intl/en-GB/gmail/about/# for details on creating an account.
•
Create the required API credential file.
•
Enable the Enable Workflow Approval through Gmail option under the Version Control properties. See Editing the Version Control server properties.

Creating a Gmail Credentials File

* 
IMPORTANT: To ensure that access to the Gmail account remains secured, Quest suggests that you store the configuration file in a location that is only accessible by the required administrators or delete it after activation.

The API credentials file allows GPOADmin to connect to Gmail, verify the authorization, get access and refresh tokens to retrieve and send messages.

For best practice information on securely using API keys see the Google Support documentation (https://support.google.com/googleapi/answer/6310037?hl=en&ref_topic=7013279).

To create the required credentials file:
1
Sign in to your Gmail account.
2
Open https://console.cloud.google.com/apis/credentials. Review the Terms of Service and click Agree and Continue.
3
Select a project and click New Project.
4
Enter GPOADmin as the project name. Leave the default Location, and click Create.
5
Click Create Credentials | OAuth client ID.
6
Click CONFIGURE CONSENT SCREEN.
7
Select the user type and click CREATE.
You can choose between Internal and External.
* 
NOTE: Internal requires a Google Workspace subscription; external allows any test user with a Google Account.
8
Enter the application name on the OAuth consent screen and click SAVE AND CONTINUE. Although some fields are optional, the following information is required:
•
App name
•
User support email
•
Developer contact information
9
To add the GMAIL API from the library, select ADD OR REMOVE SCOPES, click Google API Library link, enter GMAIL API in the Filter field, choose Gmail API, and click Enable.
After the gmail api is added, you can close the secondary Overview Gmail API tab.
10
Back on the original tab, scroll to the bottom and click UPDATE.
11
Check the Read, compose, send, and permanently delete all your email from Gmail checkbox, then click UPDATE.
12
Click SAVE AND CONTINUE to select your test users.
13
Click ADD USERS.
14
Enter the required account’s email and click ADD. (At a minimum, the account used to connect must be assigned as the test user.)
15
Click SAVE AND CONTINUE to review your settings.
16
Click BACK TO DASHBOARD.
17
Select Credentials under APIs & Services.
18
Click CREATE CREDENTIALS.
19
Select Desktop app for the Application type and optionally give it a name and click Create.
20
Click OK to close the OAuth client created dialog.
21
Click Download to download the credential information in JSON format.
This file location will be entered under the Version Control server properties when you select the Enable Workflow Approval through Gmail option.
 
 
 
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级