robot
2024.10
true
- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Azure Marketplace deployment
Robot admin guide
Last updated Dec 10, 2024
Azure Marketplace deployment
Azure Marketplace deployments allow you to deploy UiPath solutions directly from the Azure portal.
Deploying through Azure Marketplace creates a modern folder in Orchestrator. This folder comes with assigned user accounts and machine templates. The solution structure has the following naming:
- Folder:
AzureDeployed
-
User account (one for each deployed robot):
Azure-<VM Name>-<RandomString>
-
Robot account (for each user):
<VM Name>\<Machine Admin Username>
- Machine template (one for each deployed robot):
AzureTemplate-<VMName>
The Azure Portal wizard allows you to deploy one or more Robots. It uses a Windows Virtual Machine, which runs scripts to configure the Robot and connect it to Orchestrator. The machine, together with a Network Interface Card and a separate storage account, is deployed within a virtual network.
To deploy robots using the Azure Portal wizard: