Task scheduler + Remote desktop

Hello guys,

we are facing several issues regarding scheduling the robot. The robot is isntalled on the server. We are able to run it manually, but not schedule it. Also when we run it manually, and minimized or closed remote desktop, it fails at the first clicking activity. Let me summarize all questions.:

We are not able to schedule the task. Firstly, we tried schedule it with option: “Run only when user is logged on”. It seems that the robot is not able to see ui elements when the remote desktop is closed. I went through all the topics here and nothing work. My questions are: Should we definitely use Launch workflow interactive activity?? Should we somehow change the uipath.setting file? Should we use “Run whether user is logged on or not”? Should we use something different in command line than \monitored?

Thank you very much for any help.

1 Like

Hello @mario,

Maybe this will help,


1 Like

Use only Orcchestrator CE.

Task scheduler will fail or at least will be hard to maintain if you use community due to version control.

The advantages of using the Orchestrator are amazing, give it a try

i guess is this one



I have a different link here to Orchestrator CE. I don’t know if both works, but here’s my just in case:

Thanks for answers.

I have already read that article hot to schedule process manually. It didnt help.

Are you telling me that there us no solution for that? I am not even able to test it in studio. Like I said, when RDT is minimized it doesnt click on anything

Are you running inside the machine that you access with RDT? Or are trying to automate outside?

what is the difference?

If you’re automating the machine and just accessing it through RDT then the fact to minimize it shouldn’t cause any problems. But If you’re trying to automate the window of the RDT, you’re working like a Citrix Environment (VDI), so Uipath will not be able to identify the elements since it’s working with images if you minimize it.

The Robot was actualy developed on local machine and then transfered to the server. But now when I want to run it several things are not working.

The most important is the ui element interaction. The robot is not able to click on anything.

Have you tried to do the click again but this time on the Server Machine just to be sure that works? Maybe this change should have affected the developing and the server has different Ui Elements depending on the system that you are working for.

Of course. The robot runs successfully if I am sitting at the computer and watching the screen.

Once the screen is not “turned on” it fails.

HI @mario were you able to find out any reasons/solutions for this issue ?

Hi juvaraja.

I think we did. At one client we were successful. The second one has probably some restrictions from IT side. Basicly it is about correct configurarion of virtual machine. E.g. We used this


Or a mouse clicker app which moves by one picel each 100 seconds


Lots and lots users are facing this issue. This is one of big limitation of the UiPath tool. You can not schedule a project in disconnected mode (when virtual machine locked or disconnected). Even if we use launch interactive workflow, it is not consistent in behavior.

We are also getting similar issues. Without capability of running the bots in virtual desktop will defeat the purpose of automation

If you find solution, please feel to copy me in the solution. We are looking for this solution ASAP



We did find the solution.

Have u tried my link above?

In above link, the author said that the solution is not working properly.

Is there any solution for “run whether user is logged on or not” without using orchestrator?

It is working in all our cases. Where does your robot stop? At initialization of applications? The set up of server must be in line with RPA.

Hi All,
Did anyone found a workaround to this , even i am facing the same issue while triggering a uiPath workflow through Task Scheduler on locked VDI machine.
Please help


Can you explain what is not working in your case? We are able to run bots properly wo Orchestrator.

Hi Mario,
The RPA that we have is interacting with multiple systems and is running fine when we execute with the VDI machine unlocked and minimized. The RPA even runs sometimes with task scheduler but it is not consistent and fails most of the time when the VDI is locked.