- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying 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 with credential providers
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Governance
- Troubleshooting

Robot admin guide
Setting up package folders and network paths
linkRestart required!
Any update made to the config file requires a restart:
-
For Service Mode robots: restart the Robot service.
-
For User Mode robots: restart the user service, either by restarting the device or logging out of your user account and logging back in.
Setting up a fallback package folder using system environment variables
linkTo set up a fallback package folder using system enviroment variables:
- Add the
NUGET_FALLBACK_PACKAGES
variable to your system environment variables. - For the variable, add the list of the absolute paths for the folder, separated by semicolons.Important:
-
If the environment variable does not exist, the robot tries to read the NuGet packages fallback folders from the
Nuget.config
file. -
Processes deployed in fallback folders are not supported, only dependencies.
-
Setting up a fallback package folder using the NuGet.config file
linkNuGet.config
file:
- Open the
NuGet.config
file. - Add the following snippet for fallback package folders:
<configuration> <fallbackPackageFolders> <add key="Shared" value="\\server\sharedPackages" /> <add key="MachineWide" value="e:\machineWide" /> <add key="Relative" value="..\..\global" /> </fallbackPackageFolders> </configuration>
<configuration> <fallbackPackageFolders> <add key="Shared" value="\\server\sharedPackages" /> <add key="MachineWide" value="e:\machineWide" /> <add key="Relative" value="..\..\global" /> </fallbackPackageFolders> </configuration> - Save the
NuGet.config
file and restart the Robot service or the device.
Changing the download path for packages
link%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:
- Open the configuration file. You can find it in the
C:\Program Files\UiPath\Studio
folder. - In the
<packageSettings>
section, add a new entry calledpackagesInstallationFolder
. Then, set its value as the path of the new download folder. - Save the changes and restart the Robot service or the device.Note:
When changing the download folder, make sure that all users that need to run automations can access it.
For example:
<packageSettings>
<add key="packagesInstallationFolder" value="C:\Nuget" />
</packageSettings>
<packageSettings>
<add key="packagesInstallationFolder" value="C:\Nuget" />
</packageSettings>
Setting up local and network paths
linkYou 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. This is due to the way mappings are resolved per user. Since the computer account owns the installed files, it does not have access to user-specific network mappings.
Using the same shared folder for all users in High-Density environments is supported with the following 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.
|