I can speak from experience, but have not used Attended Robots to know if the license actually limits its use or not. Unattended, on the other hand, can be used attended and unattended.
I will answer your questions of what I know here:
- It’s not required but recommended. Windows client only allows 1 logon session at a time, so ideally you want to have Windows Server Environment and activate the Remote Licensing to allow more than 2 logon sessions at the same time. So, if you use a Windows client machine only 1 user can be logged at one time. (However, there are unsupported workarounds to allow more than 1)
- Also, UiPath uses alot of memory so if it isn’t a dedicated machine, users could experience performance issues. I believe you will need atleast 16mb of RAM but more than that would be helpful for a high density of jobs, especially if it is planned to use the machine with Studio as well (which will most likely happen to test and troubleshoot jobs before deploying into production)
It technically can run in the background with its “Simulate Click/Type” and “SendWindowsMessages” and “hidden” options, however its use case doesn’t really allow it to run in the background. This is because many actions require windows to be active and not every application can work as hidden in UiPath. For that reason, my answer is no it can’t run in the background. Though, it can be programmed in a way that atleast the user can’t mess it up, like testing if fields have the correct text before moving on, et cetera, except it’s still not a sure thing depending on what the job is trying to do. I did play with Autohotkey to disable the mouse and keyboard but abandoned it cause it became a pain when jobs failed, but that’s also an option.
When you RDP into a session being used for a job, it gets interfered by mouse and keyboard just like Attended. Also, once you are in that RDP session, you can’t minimize or close it because it stops the job. I have not seen a fix for that issue yet. EDIT: you can just select another window on your computer to bring it out of focus and the job will continue to run in the RDP window (I do this a lot to monitor it) while you can do other things.
I can’t answer you about a trial testing period for Unattended so you might need to ask UiPath on that one. It’s been over a year since we started, but we tested the Unattended model initially and I personally installed Orchestrator to see how it all worked to make sure it “can” work before we purchased all our additional Robot licenses.
Lastly, each machine and user id has its own set of settings, so just because a job works on one user/robot/machine, does not mean it works on another. It’s a learning process, but much of that will go away with experience.
Even though there are challenges, it still works very well for us provided the jobs are programmed with good structure and error handling, because when they are not, many inconsistencies occur.