robot
latest
false
- 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
Installing in a custom path
Guide de l’administrateur du Robot
Dernière mise à jour 17 déc. 2024
Installing in a custom path
In the advanced settings of the Robot installation, you have the option to specify a custom installation path. This allows organizations to install the Robot in a specific location, according to their IT policies, rather than using the default path suggested by the installer. However, if the custom path is outside system-controlled folders such as Windows, Program Files, or Users, the system built-in security measures may not fully protect the installation. This can expose the software to unauthorized access or tampering.
We recommend using the system-recommended default path, which is designed to be secure. But if you need to install the Robot in a custom path, consider the following best practices:
- Restrict write permissions to trusted users, such as SYSTEM or Administrators group members.
- Ensure regular users cannot modify files in the folder or gain access.