UiPath processes via Task Scheduler don’t work without an active Windows session

Help Robot
1

Hello everyone,

In our company, we have a server that we connect to via RDP. On this server, UiPath processes should run automatically.

Previously, everything worked fine with Orchestrator (Unattended), but since our license expired and UiPath no longer provides free renewal for unattended bots, we had to switch to running processes via Windows Task Scheduler.

The problem is:

  • If the Task Scheduler job is set to “Run whether user is logged on or not”, the process starts, but all UI interactions (clicks, opening windows, etc.) fail because there is no active desktop session.
  • If the job is set to “Run only when user is logged on”, then the processes run correctly, but only if the user is logged in and the RDP session is kept open. Once the RDP is disconnected, the processes stop working.

My question:
What is the best way to configure UiPath processes through Task Scheduler (without Orchestrator license) so that:

  • processes can run without keeping an RDP session open,
  • or at least the Windows session remains active after disconnecting from RDP?
2

UiPath has to have an active desktop session in order to function, or there’s no UI for it to interact with.

You’re trying to get around UiPath licensing, anyway.

1 Like
3

You shouldn’t be doing that as this is illegal to use any software without proper license or approval from UiPath.