1 |
2 |
3 |
In the Connect to Server dialog box 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. |
5 |
In the Select a Configuration Store dialog box, select AD LDS, Active Directory, or SQL for your configuration storage location. |
These are guidelines and should not be considered as an exhaustive list. |
6 |
7 |
8 |
In the Configure Server Access dialog box, after you have added all the accounts, click Finish to commit the changes. |
1 |
3 |
In the Options dialog expand License | Current License. |
4 |
Check the Update License check box and browse to and select your updated license. |
5 |
Click OK. |
To use GPOADmin with an AD LDS deployment, users must be assigned the Administrator role.
2 |
In the Select a well known Naming Context, select Configuration, then enter the console and port number in the Computer box, and click OK. |
3 |
Double-click Configuration to expand the configuration and browse to and select the Roles container. |
4 |
6 |
1 |
2 |
Select Access to add and remove users who can connect to and alter the Version Control server options. |
3 |
Select Storage to select the location of the physical backup copy of the various versions of an object. |
NOTE: To use the same AD LDS instance for both the configuration and backup store, select the “Configuration store location” option on the Backup location page. |
a |
To protect your environment from a SQL Injection attack, choose the SQL Input Filters option to specify which SQL statement inputs are not permitted within your deployment. By default, all of the inputs are marked as not permitted. |
b |
Choose the SQL Timeouts option to configure how long GPOADmin will wait to connect to the SQL server or to process a command. |
5 |
Select Desired State Configuration | Root directory to specify a DSC root directory for each domain that supports DSC scripts. This root directory serves as the starting point for the DSC script enumeration and deployment location. DSC scripts cannot be registered until this option is enabled. |
6 |
Select Scripts to set the file types that will be returned when enumerating Scripts in the live environment. Add and remove the file extensions as required and click OK. |
7 |
Select Delegation | Roles to create and edit roles that will be used to delegate rights over the Version Control system. |
8 |
Select Notifications to configure email notifications on Version Controlled events. Notifications help you to stay informed of the latest changes to objects under version control and can be enabled for Exchange on-premises, Office 365 Exchange Online, and Gmail. |
Select SMTP to modify the global SMTP notification options.
|
|
Select Workflow to enable workflow approval through email, set the authentication method, and modify the mailbox and server information.
|
To use Exchange for notifications, select Basic and enter the account to use to connect to the mailbox and password. Enter the Exchange Server Url or select Autodiscover Exchange Server Url to locate the Exchange server that is hosting the specified mailbox.
By default, GPOADmin uses the mailbox associated with the service account. If necessary, you can specify a different mailbox for the service to use when processing approvals and rejections through email. To do so, uncheck the Use the service accounts mailbox option and enter the mailbox that you want to the service to monitor. To connect as the service, leave the account blank and password blank.
To use Office 365 Exchange Online for notifications, select Exchange Online. Enter the mailbox application ID, tenant ID, tenant name, certificate, certificate password, and https://outlook.office365.com/ews/exchange.asmx as the Exchange Server Url.
|
9 |
Select Logging | Configuration to enter the log location and the type of information you want to track. |
10 |
Select Options to configure various settings. |
11 |
Select License | Current License to view the current license information. |
12 |
Select Intune | Configuration to enable support for Intune and enter the information to connect to the required Microsoft Entra tenant. This includes the application ID, tenant ID, tenant name, certificate, and certificate password for the tenant where Intune is installed. See the Minimum permissions, rights, and roles required for Microsoft Intune. |
13 |
Select Integration to configure settings that apply to a Quest Change Auditor™ integration. |
14 |
Select Enable FIPS Mode. The Federal Information Processing Standards (FIPS) are government set guidelines and standards published by the National Institute of Standards and Technology. To run a Windows environment in FIPS compliant mode, the Microsoft Policy “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” must be enabled. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center