Running Robocorp Workforce Agent Core as a Windows Service

Robocorp Cloud allows you to manage, orchestrate, and schedule the execution of your software robots in a central place. Robocorp Cloud has Processes, which contain steps that Runtime Environments execute.

This article instructs how to set up the Robocorp Workforce Agent Core as a background process on a Windows machine.

The primary purpose of running Robocorp Workforce Agent Core as a service is to essentially set up your machine as a constant Runtime Environment resource just by having the machine powered on.

Prerequisites

  • If you are not familiar with Windows Services, this might not be relevant for you.
  • To follow along, you will need a Robocorp Cloud account and Robocorp Workforce Agent Core. If you haven't already, you might want to follow the Quickstart guide to get familiar with Robocorp Cloud first.
  • You need to have administrator permissions on the machine to set up the service.

Limitations

A Windows Service does not have UI access to applications. This means that you can run so-called headless operations and access the machine and user resources, but you cannot, for example, take screenshots of Windows application UI's.

Set up the user for the service

The setup is simple if you log in to Windows as the user you want the service to run.

Generally, Windows Services can run with different permissions. In RPA cases, the reason for running on local machines is to have access to some user-level resources or permissions, so running the Robocorp Workforce Agent Core as a Windows Service requires you to use some actual user account that can be logged into.

You can set up a separate local user or use an Active Directory user.

Note: Setting up this user's permissions on the machine with the principle of least privilege is the most effective way of introducing better security.

  • TBD: A simple technical guide for setting up Windows service running just the core.