- 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
- Using EntraID users with multifactor authentication (MFA) for unattended robots
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Governance
- Troubleshooting

Robot admin guide
Restart 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.
To set up a fallback package folder using system enviroment variables:
NuGet.config file:
%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. 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:
For Service Mode robots
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.
For User Mode robots
Local path:
- You must add the
NUGET_SCRATCHenvironment 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_SCRATCHvariable. - The user accounts under which robots run must have read and write access to both NuGet folders on the machine.
<packageSettings>
<add key="packagesInstallationFolder" value="\\NetworkServer\SharedFolder\UiPath\Packages\%username%\%computername%\" />
</packageSettings><packageSettings>
<add key="packagesInstallationFolder" value="\\NetworkServer\SharedFolder\UiPath\Packages\%username%\%computername%\" />
</packageSettings>