- Getting started
- Understanding UiPath Robot
- Service Mode vs. User Mode
- Robot licensing
- 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
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Service Mode vs. User Mode
The UiPath Robot operates in two modes - Service Mode and User Mode.
Service Mode is designed for unattended automation and allows operations under locked screen or when a user is not logged in.
User Mode, on the other hand, is used for attended automation scenarios requiring human intervention. It runs from the system tray and its capabilities depend on the resources available to the currently logged-in user.
In Service Mode, the Robot runs as a Windows service, therefore it automatically starts once the system boots up. It has system-wide access, completing tasks independently, even if no user is logged into the system.
UiPath.Service.Host.exe service to handle everything related to job execution in the background.
In User Mode, the Robot starts only after a user logs in and manually launches an automation. It has the same access rights as the logged-in user. It requires a user interface to perform tasks. Without an active user session, the robot cannot run processes.
UiPath.Service.UserHost.exe service to handle everything related to job execution.
The following table summarizes the main differences between Service Mode and User Mode:
|
Robot capability |
Service Mode |
User Mode |
|---|---|---|
|
System start-up | Automatically starts at system start-up. | Starts only when the user manually launches an automation. |
|
User session | Operates independently from any specific user. | Operates under the active user session. |
|
Access rights | Has system-wide access. | Has the same access rights as the logged-in user. |
|
Execution requirements | Executes tasks even when no user is logged in. | Requires a user interface and an active user session to perform tasks. |
|
Execution resources | Requires more computational resources as it can run more complex tasks. | Needs fewer computational resources. |
|
Automation type | Suitable for unattended automation scenarios. | Suitable for attended automation scenarios. |
|
Scaling | Often used in large-scale automation deployments. | Typically used for individual or small-scale deployments. |
|
Management service | UiPath.Service.Host.exe | UiPath.Service.UserHost.exe |
|
Visibility | Mostly invisible during its operation. | Visible in the system tray and can be managed from there. |
You can switch between User Mode and Service Mode during the update process.
RegisterService parameter is added to the ADDLOCAL command.
RegisterService parameter is removed from the ADDLOCAL command.
