orchestrator

latest

false

Getting started
- Introduction
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Time-to-live Periods
- Orchestrator Outbound IP Addresses
- Notifications
Best practices
- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
- Machines
- Packages
- Audit
- Credential Stores
  - Integrating credential stores
  - Managing credential stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings
Cloud robots
- Automation Cloud™ Robots - VM
- Configuring VPN for cloud robots
- My notifications
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
Queues
- About Queues and Transactions
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
Test Suite - Orchestrator
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
- Testing Data Retention Policy
Resource Catalog Service
- About Resource Catalog Service
Authentication
- About Authentication
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
  - Managing Robots
  - Robot Statuses
  - Setup Samples
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator User Guide

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

Last updated Nov 25, 2024

Setup Samples

This page describes a mapping between a couple of various real-life scenarios and the corresponding Orchestrator setup done in classic folders.

Before proceeding to the mapping, read first how to find the username (and domain if the case) you are logged on to your machine with, and how to find the name of the machine itself.

Finding the User Name	Finding the Machine Name
To display the domain and username, follow the next steps: Open Command Prompt on that machine. Run the `whoami` command. The `domain\username` of the user is displayed.	To display the name of the machine, follow the next steps: Open Command Prompt on that machine. Run the `hostname` command. The name of the machine is displayed.

Note:

In classic folders, you can only configure floating setups of type attended. For unattended floating setups, migrate to modern folders.

Illustrative Scenarios

1 User/Machine Combination

John was provided a laptop by the company he works for, on which he works day after day.

He logs in on his laptop with using his credentials.

The unique identifier (machine name) of the laptop is JOSMITH.

Real-Life Setup
1 User 1 Machine 1 user/machine combination - stays the same day after day.

Orchestrator Floating Setup
One machine template. Its name is not relevant. One floating robot for the user. The robot is identified by John (using the `domain\username` syntax). John connects his UiPath Robot to Orchestrator using the key generated by the machine template.

Orchestrator Standard Setup
One standard machine defined using the exact name of John's workstation, namely JOSMITH. One standard robot for the user/machine combination. The robot is identified by John (using the `domain\username` syntax), and John's machine (using the standard machine entity created above). John connects his UiPath Robot to Orchestrator using the key generated by the standard machine named JOSMITH.

Orchestrator Standard Setup

One standard machine defined using the exact name of John's workstation, namely JOSMITH.

One standard robot for the user/machine combination. The robot is identified by John (using the domain\username syntax), and John's machine (using the standard machine entity created above).

John connects his UiPath Robot to Orchestrator using the key generated by the standard machine named JOSMITH.

2 User/Machine Combinations

Boris and Vadim 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.

Real-Life Setup
2 Users 1 Machine 2 user/machine combinations - stay the same day after day: {(Boris - PC345), (Vadim - PC345)

Orchestrator Floating Setup
One machine template. Its name is not relevant. Two floating robots. Both Vadim and Boris connect their UiPath Robots to Orchestrator using the key generated by the machine template.

Orchestrator Standard Setup
One standard machine defined using the exact name of the workstation, namely PC345. Two standard robots, one for each user/machine combination. One robot is identified by Vadim (using the `domain\username` syntax) and PC345 using the standard machine entity created above. One robot is identified by Boris (using the `domain\username` syntax) and PC345 using the standard machine entity created above. Both Vadim and Boris connect their UiPath Robots to Orchestrator using the key generated by the standard machine named PC345. Each standard robot needs to be defined using the respective standard machine. To retain the Type and Machine fields while creating the robots, enable the Create Another check box. Alternatively, for an already existing robot click More Actions > Duplicate.

Orchestrator Standard Setup

One standard machine defined using the exact name of the workstation, namely PC345.

Two standard robots, one for each user/machine combination.

One robot is identified by Vadim (using the domain\username syntax) and PC345 using the standard machine entity created above.
One robot is identified by Boris (using the domain\username syntax) and PC345 using the standard machine entity created above.

Both Vadim and Boris connect their UiPath Robots to Orchestrator using the key generated by the standard machine named PC345.

Each standard robot needs to be defined using the respective standard machine. To retain the Type and Machine fields while creating the robots, enable the Create Another check box. Alternatively, for an already existing robot click More Actions > Duplicate.

3 User/Machine Combinations

Randy, Kanye and Juanita work on virtual machines, on persistent virtual desktop images which are 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: RAND32,KAN43 and JUA65

Real-Life Setup
3 Users 3 Machines 3 user/machine combination which stay the same day after day: {(Randy - RAND32), (Kanye - KAN43), (Juanita - JUA65)

Orchestrator Floating Setup
One machine template. Its name is not relevant. Three floating robots. Each user connects their UiPath Robots to Orchestrator using the key generated by that same machine template.

Orchestrator Standard Setup
Three standard machines defined using the exact name of the workstations, namely RAND32,KAN43 and JUA65. Three standard robots, each for one user/machine combination. One robot is identified by Randy (using the `domain\username` syntax) and RAND32(using the standard machine entity created above). One is identified by Kanye (using the `domain\username` syntax) and KAN43 (using the standard machine entity created above). One is identified by Juanita (using the `domain\username` syntax) and JUA65 (using the standard machine entity created above). Each user connects their UiPath Robots to Orchestrator using the key generated by the standard machine with the same name as their workstation. Each standard robot needs to be defined using the respective standard machine. To retain the Type and Machine fields while creating the robots, enable the Create Another check box. Alternatively, for an already existing robot click More Actions > Duplicate.

Orchestrator Standard Setup

Three standard machines defined using the exact name of the workstations, namely RAND32,KAN43 and JUA65.

Three standard robots, each for one user/machine combination.

One robot is identified by Randy (using the domain\username syntax) and RAND32(using the standard machine entity created above).
One is identified by Kanye (using the domain\username syntax) and KAN43 (using the standard machine entity created above).
One is identified by Juanita (using the domain\username syntax) and JUA65 (using the standard machine entity created above).

Each user connects their UiPath Robots to Orchestrator using the key generated by the standard machine with the same name as their workstation.

9 User/Machine Combinations

Ion, Sandu and Georgeta work on virtual machines, on non-persistent virtual desktop images which are delivered to their endpoint devices over a network. Each day, they are arbitrarily assigned to a VM from a pool 3 VMs.

They each log in on the VMs using their credentials.

The unique identifiers of the VMs are: VM10,VM11,VM12.

Real-Life Setup
3 Users 3 Machines 9 user/machine combinations which are random {(Ion - VM10), (Ion - VM11), (Ion - VM12), (Sandu - VM10), (Sandu - VM11), (Sandu - VM12), (Georgeta - VM10), (Georgeta - VM11), (Georgeta - VM12)

Orchestrator Floating Setup
One machine template. Its name is not relevant. Three floating robots. Each user connects their UiPath Robots to Orchestrator using the key generated by that same machine template.

Orchestrator Standard Setup
Three standard machines defined using the exact name of the workstations, namely VM10,VM11,VM12. Nine standard robots, each for one user/machine combination. One robot is identified by Ion (using the `domain\username` syntax) and VM10 (using the standard machine entity created above). One robot is identified by Ion (using the `domain\username` syntax) and VM11 (using the standard machine entity created above). One robot is identified by Ion (using the `domain\username` syntax) and VM12 (using the standard machine entity created above). One robot is identified by Sandu (using the `domain\username` syntax) and VM10 (using the standard machine entity created above). One robot is identified by Sandu (using the `domain\username` syntax) and VM11 (using the standard machine entity created above). One robot is identified by Sandu (using the `domain\username` syntax) and VM12 (using the standard machine entity created above). One robot is identified by Georgeta (using the `domain\username` syntax) and VM10 (using the standard machine entity created above). One robot is identified by Georgeta (using the `domain\username` syntax) and VM11 (using the standard machine entity created above). One robot is identified by Georgeta (using the `domain\username` syntax) and VM12 (using the standard machine entity created above). Each user connects their UiPath Robots to Orchestrator using the key generated by the standard machine with the same name as their VM. Each standard robot needs to be defined using the respective standard machine. To retain the Type and Machine fields while creating the robots, enable the Create Another check box. Alternatively, for an already existing robot click More Actions > Duplicate.

Orchestrator Standard Setup

Three standard machines defined using the exact name of the workstations, namely VM10,VM11,VM12.

Nine standard robots, each for one user/machine combination.

One robot is identified by Ion (using the domain\username syntax) and VM10 (using the standard machine entity created above).
One robot is identified by Ion (using the domain\username syntax) and VM11 (using the standard machine entity created above).
One robot is identified by Ion (using the domain\username syntax) and VM12 (using the standard machine entity created above).
One robot is identified by Sandu (using the domain\username syntax) and VM10 (using the standard machine entity created above).
One robot is identified by Sandu (using the domain\username syntax) and VM11 (using the standard machine entity created above).
One robot is identified by Sandu (using the domain\username syntax) and VM12 (using the standard machine entity created above).
One robot is identified by Georgeta (using the domain\username syntax) and VM10 (using the standard machine entity created above).
One robot is identified by Georgeta (using the domain\username syntax) and VM11 (using the standard machine entity created above).
One robot is identified by Georgeta (using the domain\username syntax) and VM12 (using the standard machine entity created above).