can we have both robot service for unattended runs and UiPath studio on same vm and account?
to be able to develop and run unattended as well?
Hello @adext01,
It is possible but it is not the best practice. It might conflict in the future with your development and job run.
May I know what is your actual purpose of this?
Hi @adext01 ,
Yes, this setup is supported. You can use UiPath Studio to develop and test automations, and the same machine can also execute unattended jobs through the Robot Service. Just make sure the machine is properly licensed, connected to Orchestrator, and the account is configured as an Unattended User.
You can do that but not recommended as the unattended job can run anytime as per schedule and once finished the job, it will disconnect your connection as well.
So, if you are good and aware about the pros and cons, there is no restrictions as long as the account you are using have Unattended and Pro and Developer license allocated.
Hi @adext01,
Yes, you can have UiPath Studio and UiPath Robot on the same VM and use the same Windows account.
You can use Studio for development and testing, while the Robot Service can execute unattended jobs through Orchestrator.
The main thing is to make sure the VM, Robot/Runtime, account, and Orchestrator configuration are set up correctly for unattended execution.
For production, I would generally recommend keeping development and unattended execution separate if possible, but technically both can be installed on the same VM.
Hope this helps!
Hi @adext01,
Yes, technically you can have both UiPath Studio and Unattended Robot on the same machine. However, I don’t think this is generally followed in enterprise environments.
For hands-on practice, you can do this on your local machine, but for enterprise environments, I would recommend keeping development and unattended execution on separate VMs to avoid resource and execution/session conflicts.
Thanks!
okey thank you @ashokkarale, in the case where it’s a DEV machine and developers have access to said machine with their personal credentials, nothing changes right? we have to add the DEV machine into machine list on dev tenant, add developer accounts as robot accounts etc.. just like we would do it for a classic robot account right?
when you say the accont in question should have unnattended license, isn’t it enough to juust have a testing license on tenant and allocate it to machine? isn’t it independant from account license
This would be two users not one. The credentials should be one.
testing license also should work.
could you specify on this please: This would be two users not one. The credentials should be one.
I’d like your opinion:
do you recommend to only define one account for unattended treatments run on dev? or for each dev to be able to run unattended processes with their own accounts on VM?
basically our devs don’t have direct access to UAT and want more flexibility on unattended testing and this was an alternative
I would suggest one account for unattended.