Unattended Flow can't establish session on Virtual Machine

(0) Share

Report

Posted on by CraigSparks37

131

Greetings and Compliments for the New Year

I posted this at the end of another thread, but thought it best to have a single issue in a thread that makes sense.

I have a flow that runs great when I run it manually or on Task Scheduler.

I'm now trying to run it unattended, which I can't seem to get it to run.

If I sign out of the virtual machine or just restart it so that it is new I get

"Cannot create new session to execute unattended run."

If I just disconnect, leaving the user connected I get

"Cannot create new session to execute unattended run."

I do have an Unattended license on the user account in question.

The Cloud flow, to trigger the virtual machine desktop flow, is the same user with unattended license.

I have scheduled on the cloud flow for every 2 minutes.

I have gone through all the posts I could find around this issue,

and there is no real solution that I work use to solve this.

Any Assistance will be greatly appreciated.

Categories:

Power Automate Desktop

I have the same question (1)

All responses (6)

Answers (1)

Agnius Bartninkas Most Valuable Professional on at

Like (0)

Report

Have you tried signing out, without rebooting the machine?

Are all Power Automate services running fine on the machine?

Have you registered the machine runtime app to the environment? Have you tried running the troubleshooter on the app?

Was this reply helpful? Yes No
CraigSparks37 131 on at

Like (0)

Report

Hi @Agnius

To answer your questions.
Have you tried signing out, without rebooting the machine? Yes. Restart, connect and then sign out. also Just restart.
Are all Power Automate services running fine on the machine? Yes.
Have you registered the machine runtime app to the environment? Yes
Have you tried running the troubleshooter on the app? No, the error is in the cloud flow trying to connect to the desktop flow on the Virtual Machine.

There must be something small that I am missing..

NOTE:::::
I made a mistake in my initial post here:
If I just disconnect, leaving the user connected I get
"There is a user session on the target machine. Cannot execute unattended desktop flow."

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like (0)

Report

Is the user allowed to connect to the machine via Remote Desktop Protocol? That's what PA uses to create unattended sessions.

-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.

Was this reply helpful? Yes No
CraigSparks37 131 on at

Like (0)

Report

Yes, I tested Remoting to the machine with the credentials in the Cloud connection and I was able to connect with no issues.

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like (0)

Report

I am out of ideas. Maybe try reporting this as a bug to MS support and have them look into it. As a paying customer, you should get priority support.

Was this reply helpful? Yes No
Verified answer

CraigSparks37 131 on at

Like (2)

Report

Finally, a SORT OF Solution.

The way that Power Automate Cloud RDP Unattended was trying to connect to the VM was perfect.
After lots of investigation and pain, we found that the VM Client, in our case Citrix, was allowing the connection and then immediately terminating it.

We provisioned a Microsoft 2022 VM, placed it behind firewalls, opened the required in and outs, and it is able to establish the Unattended RDP, and run the Flow.

So the underlying issue in my case was the Citrix Client killing the connection.

Was this reply helpful? Yes No