Configure service credentials
- Updated: 2025/02/03
Continue from the Control Room installer to the Service Credentials wizard page. Use this page to specify the account that will be used to run all Windows services that are created by the Automation Anywhere installer.
Procedure
-
In the Service Credentials screen, choose from the listed
options.
The Windows Service credentials include a user name and password. The user specified must meet these requirements:
- Have permission to manage services, including Automation Anywhere services.
- If you use Windows authentication to connect to the SQL database, ensure you
grant the
db_owner
permission to the service credential user.
These service credentials allow the Control Room processes to run the required services.
- Local System Account—(default) The logged-on user
performing the installation.
-
Use a Group Managed Service Account—Specify to manage
Automation 360 services.
- Clear the Local System Account check box.
- Select the Use a Group Managed Service Account option.
- Enter the user name only. No password is required to use this option.
- Domain Account—Specify a user that is not the local
system account user
- Clear the Local System Account check box.
- Enter the user name and password for the domain account.
Use only supported characters for the user name and password. See Supported special characters in usernames and passwords.
-
- Do not use the Windows domain credentials
Enter credentials valid for running Automation Anywhere services. Without the valid credentials, the Control Room will fail to launch.
- PowerShell script restrictions
Specify a user with permissions to launch PowerShell scripts who is not a Windows domain user. Without the relevant permissions, database table creation can fail.
- Do not use the Windows domain credentials
-
Use a Group Managed Service Account—Specify to manage
Automation 360 services.
- Service Account (manually enter credential)
- Enter username.
- Enter password.
- Service Account (optionally retrieve service account credential
from the previously configured external key vault )
- If using CyberArk, enter the safe name and object name for the credential. For more information see, On-Premises initial installation using CyberArk Password Vault.
- If using AWS Secrets Manager, enter the secret name. For more information see, Integrate AWS Secrets Manager and Control Room.
- If using Azure, enter the vault URL. For more information see, Integrate Azure Key Vault and Control Room
- If using HashiCorp, enter the HashiCorp secret name. For more information see, On-Premises initial installation using HashiCorp Vault
The following example shows selection of a domain account: - Click Next.