I want to know if there is a way to control de robots that are connecting to machine templates. I have Machine A and Machine B and Robot A and Robot B. Unattended licenses. But I wan the Robot A connecting just to Machine A and Robot B connecting to Machine B. Machine standard are not available and I have both machines and robots assign to a folder in Orchestrator, but sometimes Robot A access to Machine B and I dont want that.
Hi @KevinDS
Whenever you set a trigger for your process or kick start it manually, you can choose to provide the combination there. Robot A and machine B.
Then robot A will only use machine B to run that process.
Unlike scenario, where you don’t specify anything during trigger setup or manual job run, it’s picked randomly based on which machine/robot is available at the moment.
But it’s so weird, Right know when you add a new unattended setup and select self hosted you can indicate the name of the machine, the name of the robot and this provide you of the client id and secret to add in any machine you want, so I’ve created two machine templates with differents ID for each machine. But being 2 machines into the same folder, randomly de robot that you select before for one machine could try to access another if both machines are in the same folder. I’ve tried also use de domain\user way to specify user but both users have the same password so it enters without any problem.
Hello @KevinDS
When setting up a job for execution or a trigger, you are able to define a set Account - Machine mapping.
Here you can specify the Robot User account, Machine Template and Machine which the automation must run under.
Regards
Soren
The easiest way here is to just make 2 machine templates. You must have 2 licences already since you have 2 machines active on that machine template.
Just split it into two templates, add one licence per machine, and then you can allocate them more granularly by only assigning a certain machine to certain folders.
If you then want both machines available, in the same folder, for the same process, but limit it so that each user only users a certain machine, I think the machine account mapping Soren suggests is best, however requires extra setup on every trigger / process.
However at that point I am not sure what the harm is of having the account run on both machines.