In 20.4 we’ll introduce a feature called Unattended Decoupling or, otherwise said, “breaking the robot”.
What does it mean? Suppose you have 10 machines x 10 runtimes each and 20 users. You won’t need to define anymore 200 fixed robots (userXmachine pairs) and input the password 100 times for the same user (for each 1000 machines). Instead you’ll define one machine template with 10 runtimes, 20 users and attach them to a folder. That’s all.The convention is that within a folder (which replaces the environment) any user can run/execute on any machine and the allocation is done dynamically by the Orchestrator.
This comes at a cost. The algorithm for user/machine allocation is not simple and runs on top of unattended runtimes. It will be very complicated to implement it for attended licenses therefore we’ll have to retire the scheduling and start job from Orchestrator for Studio.
Is this a big deal? For community users there is anyway one free unattended robot included and we have scheduling/reminders in tray now. Studio is made to be used in attended mode and in dev environments. For enterprise life will be simpler and machine templates/VDIs/autoscaling will run smooth.