UiPath Robot Guide

About Robot Deployment Types

Action
SCM-managed Service
User Mode Service

Attended Execution

Image

Image

Unattended Execution

Image

no_right

Concurrent Job Execution

Image

no_right

Automatic Session Management

Image

no_right

High-Density Deployment

Image

Image

Stop Service on Tray Quit

no_right

Image

Single Machine - Multi-User Deployment

Image

Image

SCM-managed Robot Service

The SCM-managed Robot Service is best suited in unattended automation scenarios and large-scale platform deployments. When a process is executed, the Robot Executor runs with the same rights as the user under which it is registered.

The Robot Service is launched by the Windows Service Control Manager under the Local System. It can open interactive Windows sessions, and has all the rights of a machine administrator. As such, it enables automatic session management (such as log on and log off) for unattended jobs. It is recommended to use the SCM-managed Robot Service for large-scale platform deployments.

Installing the Robot using UiPathStudio.msi deploys the SCM-managed Robot Service by default. It can also be installed from the Command Prompt, as explained on this page.

A SCM-managed Robot Service can easily be updated, or converted to a User Mode Robot Service. You can find out more here.

In this deployment type, the Robot is listed under Windows services in services.msc.

Jobs can be started from Orchestrator even if a user is logged in or not.

The SCM-managed Robot Service gets installed for all users on that machine. When the SCM-managed Robot Service is installed on Windows Server machines, you can run concurrent unattended jobs with automatic session management. This represents a seamless unattended automation scenario. You can have concurrent jobs with the User Mode Robot Service on a Windows Server, but not automatic session management. You can find out how to set up a Windows Server for your Robots on this page.

The UiPath.settings file is installed in the %ProgramData%\UiPath folder.

Packages are downloaded in the %userprofile%\.nuget\packages folder by default. However, you can specify a custom location when you install Studio from the Command Prompt. If you are not connected to Orchestrator, the packages you publish from Studio are saved in the %ProgramData%\UiPath\Packages folder, and become visible in the Robot Tray. Find out more about Managing Packages.

User Mode Robot Service

The User Mode Robot Service is best suited in attended automation scenarios. It runs under the user that installed it, and has the exact rights as that particular user. The Robot Agent is automatically launched when a process is started.

Installing the Robot from UiPathStudioSetup.exe deploys the User Mode Robot Service by default. It can also be installed from UiPathStudio.msi, as explained here, or the Command Prompt, as described on this page.

A User Mode Robot service can easily be updated, or converted to a SCM-managed Robot Service. You can find out more here.

In this deployment type, the Robot is not listed under the Windows services.

In order to start a job from Orchestrator, the user must be logged in. The User Mode Robot Service can not run concurrent jobs on different users, regardless if the Robot is installed on a Windows Server or not.

The UiPath.settings file is installed in the %LocalAppData%\UiPath folder.

Please note that for the SCM-managed Robot Service deployment, the .xaml files are only readable by the user that executes them.

By default, packages are downloaded in the %userprofile%\.nuget\packages folder. This location can be specified when you install Studio from the Command Prompt. If you are not connected to Orchestrator, the packages you publish from Studio are saved in the %ProgramData%\UiPath\Packages folder, and become visible in the Robot Tray. Find out more about Managing Packages.

Please note that packages downloaded by the SCM-managed Robot Service cannot be run by the User Mode Robot Service. Find out more here.


About Robot Deployment Types


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.