Elastic Robot Orchestration

Help Orchestrator
,
1

We’re considering setting up Elastic Robot Orchestration.

We are using Cloud Orchestrator and Azure Virtual Machines.

For Elastic Robot Orchestration there are two options:

  • Automatically Create Machines - single VM image
  • Manually Create Machines - multiple individual VMs

We want to manually create machines, because of VM customization.

In the documentation it says to create a new windows user, but can you use an existing user?
I want to just add the existing robot-user as administrator, since it needs to keep all the access to company programs when running jobs.

Are there limitations for what kind of jobs can be run under Elastic Robot Orchestration?

“Do not join the virtual machine to a domain.” What does this mean, and does it apply to custom set up VMs also?
The documentation is not clear when setting up custom VMs:

EDIT:
If you’re providing the VMs in Elastic Orchestration, aka “Manually Create Machines”:

Folder → Settings → Manage Access: Add ‘Automation User’ to your robot account.
Log onto VM, connect Assistant to Orchestrator (this info is missing in the documentation)
(No need to create an additional local user).

Look under Tenant → License, that your machine has the Elastic Template and License status is active.

2

Hey @Ferdinand

Yes, you can use an existing Windows user for your robots as long as:

  • That user has the necessary permissions, usually Local Administrator access (required for UiPath robot services).
  • The user has all the program access, environment variables, etc. needed for automation.
  • You configure that existing user correctly in Orchestrator (i.e., as a robot user with attended/unattended permissions).

Many organizations use pre-configured users for this exact reason — to retain access to licensed or pre-installed apps.

So yes — you can use an existing robot-user account, especially if it’s already tuned for automation.

2. “Do not join the virtual machine to a domain” — what does it mean? Does it apply to manual VM setups?

This is only required when using the Automatically Created Machines (ACM) setup. In that mode, Orchestrator uses Machine Templates + Azure scaling, and the VMs must be non-domain joined for automated deployment and management.

In Manual Machine mode (which you’re using), you can join VMs to a domain — in fact, it’s common for enterprises to use domain-joined machines to manage policies, apps, and security centrally.

So this part of the documentation does not apply to your setup.

  1. Are there limitations to what kind of jobs can be run with Elastic Robot Orchestration?

There are no direct limitations on job types, but there are some considerations when using ERO:

  • ERO dynamically allocates machines, so your robot user and VM image must be fully ready to run jobs the moment the machine is spun up or scheduled.
  • If the robot relies on:
    • Local-only dependencies not present on the base image
    • Interactive prompts (dialogs, MFA, etc.)
    • Domain-level policies or login scripts that slow login or block unattended access Then you might hit unexpected behavior.

In Manual Machine mode, since you control the VMs, you avoid most of these issues, as long as your VMs are:

  • Always on (or reliably available)
  • Correctly configured for unattended execution (robot service, resolution, permissions, etc.)

cheers

1 Like
3

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