robot
2022.4
false
Robot User Guide
- Release notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Restarting Robot Components
- Governance
- Troubleshooting
- About Troubleshooting
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
Azure marketplace deployments allow you to deploy UiPath solutions directly from the Azure portal.
UiPath® Robot
The deployment will create a modern folder in a UiPath® Orchestrator with Users and Machine Templates assigned to it. For attended robots, the UiPath® Orchestrator must have attended robots licenses. The names are as follows:
- Folder:
AzureDeployed - User (one for each robot deployed):
Azure-<VM Name>-<RandomString>- Robot user (for each user):
<VM Name>\<Machine Admin Username>
- Robot user (for each user):
- Machine Template (one for each robot deployed):
AzureTemplate-<VMName>
The Azure Portal wizard will allow you to deploy one or more UiPath® Robots. The components are:
| Name | Details |
|---|---|
| Windows Virtual Machine | Virtual Machine that will run scripts to configure the UiPath® Robot and connect it to the UiPath® Orchestrator. It gets deployed in a VNet together with a Network Interface Card and a separate storage account. |
Going Through the Wizard
Basics
In this step, you need to select the subscription, the Resource Group, and Region where you want the solution to be deployed.
| Name | Details |
|---|---|
| Subscription, Resource Group, and Region | Please select the subscription, the Resource Group, and Region where you want the solution to be deployed. |
| Virtual Machine Name | Provide a name for the Virtual Machine(s). If multiple and index will be added. |
| Username | Set the administrator user for the Azure Virtual Machine |
| Password | Virtual Machine password |
| Number of VMs/Robots | Enter the number of UiPath Robots you need. |
Orchestrator Connection Info
| Name | Details |
|---|---|
| Orchestrator URL | The URL of an existing and licensed Orchestrator |
| Orchestrator Admin Account | Orchestrator admin account with API usage permissions. |
| Orchestrator Admin Password | Password for the aforementioned admin account |
| Orchestrator Tenant | Name of the tenant you want the robot to be connected to. |
| Type of Robot | Available robot types: Attended, Unattended |
| Robot Version | Select the version for the UiPath® Robot |
VM Settings
| Name | Details |
|---|---|
| Virtual Machine Size | The size of the Robot VM. |
| Public IP Address for VM | The public IP name for each Robot (index appended if needed). |
| DNS Prefix for PIP | DNS Prefix for the public IP Address must be globally unique. Index appended if needed. |
| UiPath® Robot(s) VNet | Name of existing or new VNet. |
| Subnet | Subnet used for the UiPath® Robot VMs. |
Tags Configuration
Here you can create tags for the resources created in the deployment.