Robot Installation

Dear Forum Members,

there are two options when installing a Robot

  1. Install Robot in Usermode
  2. Install Robot as a windows service

Is someone with experience in this matter aware of the difference between the above two Robot installation types?


Buddy @haider8645

may be this could help you




A Robot is installed as a Windows Service by default. As a result, the Robot can open Windows sessions (interactive or non-interactive), under the Local System account, and has all the rights of a Windows service. 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.

Robots can also be installed in a user mode. For your Robot, this means that it has the exact same rights as the user under which it has been installed. 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.



Many thanks for sharing the links. I went through “About Robot Deployment Types”. I have found a conflicting statement between the Robot as a SCM Service and Robot in User Mode as shown in figures below. Do you know which statement is true for the User Mode concurrent jobs on windows server?


This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.