- 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
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- 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
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting

Robot admin guide
Job executions
The UiPath Robot executes jobs across different operational environments:
-
The Robot can execute tasks in Windows sessions, either as a console or RDP session, depending on the Orchestrator LoginToConsole setting.
-
The Robot can concurrently run multiple background automations in the same Windows session, with each automation having its own set of dependencies.
-
The Robot can operate in Linux environments via Linux Robots, providing cross-platform automation within a functional Linux environment, made possible by a Docker image.
-
The Robot can function in High-Density environments where multiple robots run concurrently under different user accounts on Windows Server machines.
-
The Robot can operate through Citrix Apps virtualization, which allows it to be set up on a central server and delivered to devices via Citrix virtualization technology.