- 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
Setting up package folders and network paths
%userProfile%\.nuget\packages
.
UiPath.config
file, or use the PACKAGES_FOLDER="new/download/path"
parameter via the command line when installing Studio or Robot.
UiPath.config
file, follow these steps:
For example:
<packageSettings>
<add key="packagesInstallationFolder" value="C:\Nuget" />
</packageSettings>
<packageSettings>
<add key="packagesInstallationFolder" value="C:\Nuget" />
</packageSettings>
You can set a local or network path to enable several robots to use the same path. The setup depends on the robot operational mode: Service Mode or User Mode.
On Windows Server machines that allow concurrent executions on High Density Robots, you need to set up unique paths for each user. Using the same shared folder for all users in High Density environments is supported with some limitations:
Robot mode |
Path type |
Considerations for multiple robots using the same path |
---|---|---|
Service mode |
Local path |
No restrictions |
Network path |
| |
User Mode |
Local path |
|
Network path |
The path must include the machine name and username.
|