robot
latest
false
UiPath logo, featuring letters U and I in white

Robot admin guide

Last updated Jan 23, 2025

Setting up package folders and network paths

Setting up a fallback package folder

To set up a fallback package folder using system enviroment variables:

  1. Add the NUGET_FALLBACK_PACKAGES variable to your system environment variables.
  2. 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.

Changing the download path for packages

The default download path for packages is %userProfile%\.nuget\packages.
To change the package download location, you can either edit the UiPath.config file, or use the PACKAGES_FOLDER="new/download/path" parameter via the command line when installing Studio or Robot.
To edit the UiPath.config file, follow these steps:
  1. Open the configuration file. You can find it in the C:\Program Files\UiPath\Studio folder.
  2. In the packageSettings section, add a new entry called packagesInstallationFolder. Then, set its value as the path of the new download folder.
  3. Save the changes and, if the Robot is installed as a service, restart the service.
    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

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. 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

  • Not supported when Secure XAML is used.

  • Service mode robot installed on separate machines must have its own folder on the network.

  • Mapped network paths, such as Z:\Packages, are not supported. Use non-mapped path, such as \\server\Packages.

User Mode

Local path
  • You must add the NUGET_SCRATCH environment variable on the robot machine, and provide it with a value other than the NuGet installation one. This sets a different path for storing temporary NuGet files, to prevent potential conflicts when multiple robots attempt to use NuGet simultaneously.
  • The new temporary folder should be exclusive for the NUGET_SCRATCH variable.

  • The user accounts under which robots run must have read and write access to both NuGet folders on the machine.

Network path

The path must include the machine name and username.

<packageSettings>
  <add key="packagesInstallationFolder" value="\\NetworkServer\SharedFolder\UiPath\Packages\%username%\%computername%\" />
</packageSettings><packageSettings>
  <add key="packagesInstallationFolder" value="\\NetworkServer\SharedFolder\UiPath\Packages\%username%\%computername%\" />
</packageSettings>

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo White
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.