robot
2024.10
true
- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for 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
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Using network locations
Robot admin guide
Last updated Nov 12, 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.