- Démarrage
- Comprendre UiPath Robot
- Assistant UiPath
- Prérequis d’installation
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Configuration de Windows Server pour des Robots haute densité
- Rediriger les Robots vers un serveur proxy
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Configurer des Robots Linux
- Configuration de la vérification de la signature des paquets
- Configurer des dossiers de package et des chemins d’accès réseau
- Configurer des flux d’activité
- Setting up non-persistent VDIs - follow up with Sai
- Installing robots for attended automations
- Configuring robots for attended automations
- Intégrations
- Résolution des problèmes
- Résoudre les problèmes du service de robot UiPath
- Résoudre les problèmes d’exécution
- Résoudre les problèmes de mise en réseau
- Résolution des problèmes de connexion
- Licensing troubleshooting
- Package troubleshooting
- Résolution des problèmes .NET
- Dépannage de la journalisation
- Dépannage des problèmes de session
Guide de l’administrateur du Robot
Installer via des modèles de déploiement
Deploying Service Mode Robots on AWS infrastructure allows you to run unattended automations on Amazon EC2 instances.
Les options de déploiement suivantes sont disponibles :
Les déploiements place de marché Azure vous permettent de déployer des solutions UiPath directement à partir du portail Azure.
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:
- Dossier :
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:
- On the Basics panel:
- Select the Subscription, the Resource Group, and the Region where you want your solution to be deployed.
- Provide a Virtual Machine name.
- Set the Username for the administrator of the virtual machine (VM).
- Provide the Password to access the VM.
- Specify the Number of virtual machines with robots to be created.
- On the Orchestrator Connection Info panel:
- Provide the Orchestrator URL of an existing and licensed instance.
- Provide the username of the Orchestrator admin account that has API usage permissions.
- Provide the Password for the Orchestrator admin account.
- Provide the Orchestrator Tenant Name where the robot should connect.
- Select the Robot type.
- Select the Robot version.
- On the Virtual Machine Settings panel:
- Set the Virtual machine size.
- Select the Public IP Address for the VM.
- Provide the DNS Prefix for the public IP Address.
- Select the Virtual network.
- Select the Subnet for the VM.
