Robot
2023.4
false
Banner background image
Robot User Guide
Last updated May 13, 2024

Robot Service

The robot service is the brain of all operations. It communicates through an inter-process communication channel with Studio , theUiPath® Assistant, andRobot Command Line Interfaceto receive and process information, and then to provide the necessary instructions to theRobot Executor.

The robot service is also responsible for sending the Robot heartbeat to Orchestrator, communicating execution status or receiving new execution orders, and acting as a proxy between Orchestrator and the execution hosts.

Windows sessions in which processes are executed are managed and monitored by the Robot service, while also being trusted with the credentials for Robots.

The robot service can be deployed in service mode or user mode. The main differences are presented in the table below:

Action

Service Mode Robot

User Mode Robot

Attended Execution

available

available

Unattended Execution (Automatic Session Management)

available

not available 1

Concurrent Job Execution

available

available

Single Machine - Multi-User Deployment

available

available

1Unattended execution with the User Mode Robot is possible only while the user is logged in with an active session.

The Service Mode Robot service

The Service Mode Robot is best suited to unattended automation scenarios. When a process is executed, the Robot Executor runs with the same rights as the user under which it is registered.

The Service Mode Robot service:

  • UsesUiPath.Service.Host.exeand an additional per-user service (UiPath.Service.UserHost.exe) for each user on the machine.
  • Is launched by the Service Control Manager (SCM) under the Local System user.
  • Can open interactive Windows sessions.
  • Is best suited for unattended automation scenarios and large-scale platform deployments.
  • Has the rights of a machine administrator.
  • Is listed under Windows services.
  • Can execute jobs from Orchestrator even if a user is not logged in by starting a session.

Additionally:

  • TheUiPath.settingsfile is installed in the%ProgramData%\UiPathfolder.
  • Packages are downloaded in the%userprofile%\.nuget\packagesfolder by default.
  • Local packages are saved in the%ProgramData%\UiPath\Packagesfolder, and are available in the Assistant.

    A Service Mode Robot can be easily updated or converted to a User Mode Robot.

    Note: When converting the Robot from Service-Mode to User-Mode, the Robot might not be able to access the.xamlfiles from the original NuGet Packages folder. For details on how to resolve this, please readthis guidewhich offers more details on this specific scenario.

The User Mode Robot service

The user-mode robot is best suited to attended automation scenarios. It runs under the user that starts it, and has the exact same rights as that particular user.

The User Mode Robot service:

  • Only usesUiPath.Service.UserHost.exeand is launched automatically by Studio or UiPath® Assistant.
  • Is best suited for attended automation scenarios.
  • Has the rights of the user that runs it.
  • Is not listed under Windows services.
  • Requires a user to be logged in with an active session to execute jobs from Orchestrator.

Additionally:

  • TheUiPath.settingsfile is installed in the%LocalAppData%\UiPathfolder.
  • Packages are downloaded in the%userprofile%\.nuget\packagesfolder.
  • Local packages are saved in the%ProgramData%\UiPath\Packagesfolder and are available in the Assistant.

    A User Mode Robot can easily be updated or converted to a Service Mode Robot .

  • The Service Mode Robot service
  • The User Mode Robot service

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.