- 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)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Classic Robots
- Troubleshooting
Managing Robots
In classic folders you can connect UiPath Robot to Orchestrator:
- using attended floating robots in conjunction with machine templates
- using all types of standard robots in conjunction with standard machines
- You need the Robots - Create and Machines - View permissions.
- You must know the username that is used to access the machine.
- You must know the password for the specified username (only required for Unattended Robots).
- You must know the name of the machine on which UiPath Robot is installed. You may find it in the UiPath Robot tray, on the
Orchestrator Settings window, or in Control Panel (
Control Panel/System and Security\System).
- Select the classic folder on the left menu.
- Along the top, click Robots. The Robots page opens.
-
Click Add in the top right of the page and select Standard Robot. The Create a New Standard Robot window opens:
- In the Machine field, select a previously created standard machine, or type a new machine name to create a new one. The standard machine needs to have the exact same name as the machine on which UiPath Robot is installed.
- In the Name field, type a name for the robot.
- Add a description for the robot. We recommend populating this field, especially when dealing with an environment with many robots.
-
From the Type drop-down list, select the desired license type for the robot.
Important: The first unattended robot created on a machine automatically assigns a runtime license of that type to the machine, if that machine has none defined. Robots created afterwards have no subsequent impact on the runtime number. You can edit the runtimes number on the Machines page or on the License page.Note: For RPA Developer, RPA Developer Pro, or Citizen Developer licenses, if they are already licensed locally, select the Stand-alone license check box, as this ensures Orchestrator does not allocate a license from its pool of licenses. - In the Credential Store field, select where the credentials for this robot are stored (only required for unttended robots).
- In the Domain\Username field, type the username that is used to log in to the specified machine using the
machine_name\usernamesyntax. If the user is in a domain, you are required to specify it in aDOMAIN\usernameformat. You must use short domain names, such asdesktop\administratorand NOTdesktop.local/administrator. - In the Password field, fill in the Windows password for the user (only required for Unttended Robots). If you are using SmartCard authentication, check the The password represents a SmartCard Pin option and fill in the corresponding SmartCard PIN instead.
- Navigate to the Settings tab if you want to change the default robot settings. Make the desired changes, if any.
- If you want to create another robot of the same type and on the same machine, but for a different user, at the bottom, select Create another. If selected, the current Machine and Type values are retained for creating the next robot.
- Click Create. The robot is now provisioned to Orchestrator and displayed on the Robots page. The robot appears offline until the corresponding UiPath Robot installed on the machine connects to Orchestrator.
- You need the Robots - Create permission.
- You must know the username that is used to access the machine.
- Select the classic folder on the left menu.
- Along the top, click Robots. The Robots page opens.
-
Click Add in the top right of the page and select Floating Robot. The Create a New Floating Robot window opens:
- In the Name field, type a name for the robot.
- Add a description for the robot. We recommend populating this field, especially when dealing with an environment with many robots.
-
From the Type list, select the license type for the robot.
Note: In classic folders you can only create attended floating robots.Note: For RPA Developer, RPA Developer Pro, or Citizen Developer licenses, if they are already licensed locally, select the Stand-alone license checkbox, as this ensures Orchestrator does not allocate a license from its pool of licenses. - In the Domain\Username field, type the username that is used to log in to the specified machine. If the user is in a domain, you are required to
specify it in a
DOMAIN\usernameformat. You must use short domain names, such asdesktop\administratorand NOTdesktop.local/administrator. - Navigate to the Settings tab if you want to change the default robot settings. Make the desired changes, if any.
- If, after you're done, you want to create another robot with the same Type, select Create another.
- Click Create. The robot is now provisioned to Orchestrator and displayed on the Robots page. The robot appears offline until the corresponding UiPath Robot installed on the machine connects to Orchestrator.
Click More Actions > Edit, make the necessary changes, and then click Update.
When a Robot is busy (executing a process), you cannot edit the following information:
- Domain\Username
- Machine
- Type
Duplicate the configuration of an existing robot, so that you can create a new one for a different user on the same machine.
Click More Actions > Duplicate for the robot you want to duplicate. A new window is displayed which retains the machine and type of the duplicated robot. Fill in the robot name, new username (and password for unattended robots) and click Create.
Click More Actions > Convert to Floating for the standard robot you want to convert. Only Attended, RPA Developer, or Citizen Developer standard robots can be converted to floating robots.
Click More Actions > Monitor Robot for the respective robot. Alternatively, select it from the Robots Overview widget (Monitoring > Robots > Folder Overview).
Click the More Actions > Remove for the respective robot.
Alternatively, select one or multiple Robots from the Robots page and click Remove.
This feature simplifies robot migration from classic folders to modern folders as you are presented with a rollback option if a step errors out during migration. You can only disable robots in the following connection states: active, disconnected, unresponsive.
The following associated entities are impacted when disabling a robot:
- Licenses - Licensing metrics do not take into account deactivated robots.
- Jobs - Deactivated robots cannot execute jobs.
- Triggers - When configuring triggers, the displayed robots have an associated Active toggle that illustrates the robot's availability state and allows you to enable/disable the robot. If you scheduled a job on a pool of deactivated robots, an error is thrown at the job creation.
- Assets per Robot - When configuring assets, deactivated robots are available for selection.
-
Environments - When managing environments, deactivated robots are available for selection.
Note: Reenabling the robot renders all impacted entities usable.
