- Getting started
- Best practices
- Tenant
- 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
- Configuring automation capabilities
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Authentication
- Integrations
- Classic Robots
- Troubleshooting
Machines
Machines are Orchestrator objects that help administrators configure unattended infrastructure settings. For the purpose of this guide, we assume a machine is the machine object in Orchestrator and that a host machine represents a workstation (physical or virtual) on which a UiPath® Robot is installed.
The main functions of a machine object are:
- Authorizing the connection between the UiPath Robot and Orchestrator. Depending on the type of robot authentication set on your tenant, authorization can happen either via a machine key or via a client ID-client secret pair. Learn more about robot authentication.
- Controlling the execution capacity on the host machines the UiPath Robot resides.
- Specializing host machines in executing particular types of processes.
Machine objects are global resources, meaning they are available across folders.
A machine template enables you to connect UiPath Robots deployed on multiple host machines to Orchestrator, regardless the names of the host machines or the users logging onto them.
Machine templates, as their name suggests, work as templates whose settings apply to groups of host machines with the same physical setup. When grouping host machines under the same machine template, we recommend you follow these practices:
- the host machines have been deployed based on a shared template, or at least configured as if they were.
- the same applications should be installed on the machines, and quite importantly, the applications should be installed at the same paths on each of the machines, and they should all share the same version of the applications.
- the users logging into the applications on these machines should all have the same access rights to the applications on them.
When a new Tenant is created, the system automatically creates a machine template with the name Shared. This name is reserved at the system level. You are not able to create a machine template with the name Shared.
In order to be able to perform various operations on the Machines page, you need to be granted the corresponding permissions on Machines:
- Viewing a machine and machine-related details View on Machines
- Editing a machine - Edit on Machines
- Creating a machine - Create on Machines
- Deleting a machine - Delete on Machines
- Changing account-machine mappings at the tenant level - View on Machines, Edit on Machines OR View on Machines, Create on Machines
- Changing account-machine mappings at the folder level - Edit on Folders OR Edit on Subfolders
Read more about roles.
