robot
2024.10
true
- Démarrage
- Comprendre UiPath Robot
- Assistant UiPath
- Prérequis d’installation
- Installing robots for unattended automations
- Configuring robots for 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é
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Intégrations
- Résolution des problèmes
Using network locations
Admin Guide
Last updated 21 oct. 2024
Using network locations
For easier access to shared network folders, you can map network drives on your user account. To map a network drive is to connect a network location that can be accessed via a URL, such as
\\ServerName\SharedFolder
, to a drive letter, such as z:
.
Important :
The mapping of a network drive is user-specific. So access to a mapped network drive is limited to the individual user for whom the mapping was done.
However, if you store the packages published from Studio on the mapped network drive, you might run into some issues. To prevent this, map the network drive for the Local System.
Occasionally, robots cannot find a mapped network drive when running an unattended automation. This can happen due to the non-interactive nature of the session 0.
To prevent this, map the network drive in
headless
mode. This can be done by remapping the drive for every job the robot starts. The remapping must be applied when the machine is restarted.
In the unattended automation workflow, explicitly run the
net use Z: \\unc\path
command before accessing the shared drive.