- Getting started
- Best practices
- Tenant
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring system email notifications
- Audit logs for the host portal
- Maintenance Mode
- Organization administration
- Troubleshooting
Setup Samples
This page describes a mapping between various real-life scenarios and the corresponding Orchestrator setup.
John was provided a laptop by the company he works for, on which he works day after day.
He logs in on his laptop using his credentials.
The unique identifier (machine name) of the laptop is JOSMITH.
- 1 Account
- 1 Machine
-
1 account/machine combination - stays the same day after day.
Orchestrator Setup
One machine template.
One floating robot for the user. The robot runs under John's user account and is identified using thedomain\usernamesyntax. Floating robots are automatically created at the user level.John connects his UiPath Robot to Orchestrator using the key generated by the machine template.
John and Jane work as call center operators. They work in 2 shifts on the same computer.
They each log in on the computer using their credentials.
The unique identifier of the laptop is PC345.
- 2 Accounts
- 1 Machine
-
2 account/machine combinations - stay the same day after day: {(John - PC345), (Jane - PC345)}.
Orchestrator Setup
One machine template.
Two floating robots. Floating robots are automatically created at user level.
Both John and Jane connect their UiPath Robots to Orchestrator using the key generated by the machine template.
John, Jane, and Alice work on virtual machines, on persistent virtual desktop images delivered to their endpoint devices over a network. Each of them uses the same VM day after day.
They each log in on the VMs using their credentials.
The unique identifiers of the VMs are JOH32,JAN43, and ALI65
- 3 Accounts
- 3 Machines
-
3 account/machine combination which stay the same day after day: {(John - JOH32), (Jane - JAN43), (Alice - ALI65)}
Orchestrator Setup
One machine template.
Three floating robots. Floating robots are automatically created at user level.
Each account connects their UiPath Robots to Orchestrator using the key generated by that same machine template.
John, Jane, and Alice work on virtual machines, on non-persistent virtual desktop images delivered to their endpoint devices over a network. Each day, they are arbitrarily assigned to a VM from a pool of 3 VMs.
They each log in on the VMs using their credentials.
The unique identifiers of the VMs are: VM10,VM11,VM12.
- 3 Accounts
- 3 Machines
-
9 account/machine combinations which are random {( John- VM10), (John - VM11), (John - VM12), ( Jane- VM10), (Jane - VM11), (Jane - VM12), (Alice - VM10), (Alice - VM11), (Alice - VM12)}
Orchestrator Setup
One machine template.
Three floating robots. Floating robots are automatically created at user level.
Each account connects their UiPath Robots to Orchestrator using the key generated by that same machine template.
