- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- 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
- 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
- Setting up non-persistent VDIs - follow up with Sai
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Robot admin guide
Linux robots
Before the introduction of Linux Robots, UiPath Robots were confined to Windows operating systems, as they were built to interact with Windows-specific technologies.
To expand your automation scope beyond Windows-exclusive operability, we introduced Linux Robots.
A Linux Robot is a version of the Robot built to function in Linux environments, therefore making cross-platform automation possible.
The Robot, together with the Linux operating system and other software dependencies, are bundled into a Docker image. When you use this image to start a Docker container, the resulting container would be a standalone, functional Linux environment where the Robot can operate.
mcr.microsoft.com/dotnet/runtime
. All files required by the application are found in the /application/
directory.