Windows Server 2016 configuration for GUI robots

Currently we are testing capabilities of UiPath to deal with our tasks using UiPath CE with Orchetrator CE.

We want to handle simple GUI applications on Windows Server 2016 running on Virtual Machine. While remote connection everything is running properly when task is triggered from studio or orchestrator. When we close remote connection we are able to launch task from orchetrator but after couple minutes we get Failure status. After connection we can observe that all non GUI actions (create text file, append text file, start process) run correctly till the first GUI action (click button, write to textbox etc.).

Does anyone handled similar problem? How we can configure Windows or UiPath robot to handle those problems and prepare for system auto startup.

@Dawid_P we have a similar problem with our setup. When we when we disconnect from a remote session, the robot cant click any where.

Did you find a solution to your problem?

Hi @mkz

I think this snippet of our documentation is relevant here:


Same principles should apply when automating on a locked/closed session.