I have hunted for days, but cannot find my situation.
I have a Studio license on a shared machine. That machine is connected to a package in Orchestrator and is assigned the Studio Robot of the shared machine. I want to be able to log in to Orchestrator from my machine (AD single sign-on) and kick off the process on the Server. This worked great in v2019.10 but I just upgraded to v2020.10 and can no longer start the process. I no longer have any robots to choose from in the Execution Target area of the Start Job screen even though my robot looks active (see picture). The problem is that there are resources on this shared machine not accessible from anywhere else. I have a Studio license (which worked before) and an Attended license that I could never get to work - though I think I now got this working to the level of the Studio license, so not really working.