- Getting started
- Introduction
- User Options
- Logging in to Orchestrator
- Resetting Your Password
- My Profile
- Robots
- Robot Statuses
- Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
- Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Folders
- Managing Folders
- Classic Folders Vs Modern Folders
- Migrating From Classic Folders to Modern Folders
- Administration of Modern Folders
- Personal Workspaces
- Managing Personal Workspaces
- Monitoring
- Unattended Sessions
- User Sessions
- License
- Managing Access and Automation Capabilities
- Assigning Roles
- Managing Roles
- Default Roles
- FAQ
- Machines
- Managing Machines
- Assigning Machine Objects to Folders
- Configuring Account-machine Mappings
- Packages
- Managing Packages
- About Libraries
- Managing Libraries
- Audit
- Credential Stores
- Managing Credential Stores
- CyberArk® Integration
- CyberArk® CCP Integration
- Azure Key Vault Integration
- HashiCorp Vault Integration
- BeyondTrust Integration
- Webhooks
- Types of Events
- Managing Webhooks
- Licensing
- Managing Your Licenses
- Alerts
- Setting Up Alert Emails
- Settings
- General Tab
- Deployment Tab
- Robot Security Tab
- Scalability Tab
- Non-Working Days Tab
- Resource Catalog Service
- About Resource Catalog Service
- Folders Context
- About the Folders Context
- Home
- Automations
- About Automations
- Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- About Recording
- Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Triggers
- About Triggers
- Managing Triggers
- Using Cron Expressions
- Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Orchestrator Logs
- Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
- Exporting usage data
- Queues
- About Queues and Transactions
- Queue Item Statuses
- Business Exception Vs Application Exception
- Studio Activities Used With Queues
- 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)
- Storage Buckets
- About Storage Buckets
- CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
- Orchestrator testing
- 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
- Managing Test Data Queues in Orchestrator
- Managing Test Data Queues in Studio
- Field Descriptions for the Test Data Queues Page
- Test Data Queue Activities
- Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
- 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
- Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
- Reconfiguring authentication after upgrade
- Allowing or restricting basic authentication
- Configuring SSO: SAML 2.0
- ADFS Authentication
- Google Authentication
- Okta Authentication
- PingOne Authentication
- Custom Mapping
- Self-signed Certificates
- Private Key Certificates
- Configuring SSO: Google
- Configuring SSO: Azure Active Directory
- Configuring the Active Directory Integration
- Switching between Active Directory adapters
- Managing your host license
- Allocating Licenses to Tenants
- Configuring system email notifications
- Configuring other host settings
- Customizing the Login page
- Session Policy
- Orchestrator host settings
- Audit logs for the host portal
- Maintenance Mode
- Organization administration
- About organizations
- Managing organization administrators
- Configuring organization authentication
- Allowing or restricting basic authentication
- Setting up the Azure AD integration
- Configuring the SAML integration
- Configuring security options
- Licensing
- Activating your license
- Accounts and Groups
- About accounts and groups
- Managing accounts and groups
- Managing access
- Registering External Applications
- Managing External Applications
- Overriding System Email Settings
- Audit Logs
- Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors
- Cron Expressions
- Upgrade troubleshooting
Orchestrator user guide
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:
|
To display the name of the machine, follow the next steps:
|
In classic folders, you can only configure floating setups of type attended. For unattended floating setups, migrate to modern folders.
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. |
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.
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.
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. |
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.
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. |