- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read Only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Test Automation
- Host Administration Portals
- Configuring System Email Notifications
- Managing System Administrators
- Configuring Host Security
- Host Audit Logs
- Customizing the Login Page
- Maintenance Mode
- Managing tags
- Audit Logs
- Overriding System Email Settings
Configuring Robot Accounts to Run Unattended Automations
Unattended automation typically runs on robot accounts, the UiPath equivalent of Windows service accounts. Robot accounts can be thought of as non-human identities that need to be authorized to access Orchestrator resources. Their association with roles allows for a certain level of access to resources in Orchestrator. Learn about access control in Orchestrator.
Robot accounts have their unattended capabilities enabled by default, administrators only have to configure several infrastructure related settings.
To configure unattended execution settings under a certain robot account and on specific infrastructure, an administrator must do the following when referencing or editing the robot account in Orchestrator:
- Click the Unattended setup tab to configure execution settings for the account.
- In the Foreground automations settings section, select the infrastructure to be used for executing unattended foreground processes under that account:
- Select the Use a specific Windows user account. Add credentials below option to execute processes on a specific Windows machine. You must specify correct credentials for that host machine, such
that the robot can log into it successfully. This allows running processes that require user interaction under that specific
Windows account. Here's how to configure the credential settings when using specific Windows accounts:
The account under which the robot runs.
- For domain-joined accounts, use the
domain\usernamesyntax. For example
- For local Windows accounts, use the
host_machine_name\usernamesyntax, with the host machine's name instead of the domain. For example,
- For local Windows accounts residing on multiple host machines, which you want to use regardless of machine, use the
.\usernamesyntax with a dot instead of the host machine name. For example
- For Azure AD joined machines, use the
The credential store to be used for your password. Click here for details about credential stores.
The password used to log on to the machine on which UiPath Robot is installed.
Specifies the type of password credential.Note: Unattended robots can run background jobs on any infrastructure. It is, however, recommended to specialize your host machines to execute particular types of processes in order to maximize efficiency and cut costs. Learn more about optimizing unattended infrastructure using machine templates.
- For domain-joined accounts, use the
- Select the Use a specific Windows user account. Add credentials below option to execute processes on a specific Windows machine. You must specify correct credentials for that host machine, such that the robot can log into it successfully. This allows running processes that require user interaction under that specific Windows account. Here's how to configure the credential settings when using specific Windows accounts:
- Enable the Run only one job at a time option to restrict the account from simultaneously executing multiple jobs. This helps when automating applications that do not allow for a credential to be be used more than once at a time (e.g., SAP).
- On the Robot settings tab, configure execution settings for the unattended robot. Learn about robot settings.
- Click Add or Update. The robot account is created/updated.