I was planning to upgrade to the latest UiPath and I found some terms are changed, e.g. we used to use back office robots and they are now renamed to unattended robots under 2017.1. So I got questions here,
Unattended robots and back office robots - are they the same (only changed the name)?
Can we start unattended robots/processes without Orchestrator?
As per the info i have It is possible to run unattended Robot without Orchestartor. If the Robot is not connected to Orchestrator, you can still license it locally: Licensing a Robot.
If you have Unattended license key, it will know to “behave” as Unattended.
If we locally licensed the Robot as Unattended, it can do work as unattended Robot without connecting to Orchestrator.
That robot can run under locked screen, but you will first have to be logged in to the Robot machine, run your process manually, then lock your screen. Also there is this possibility to run the unattended robot using command line: or schedule it using windows task scheduler.
If you connect it to Orchestrator and run through Orchestrator you won’t need to have access to the Robot machine and you can run your process(Start a Job) from anywhere.
Please keep in mind that TaskScheduler execution is no longer supported singe 2017.1 version. The command line arguments and the way in which the robot behaves if it is started from a Windows scheduled task might change at any time without any prior notification.
As I have answered in PM, and as Andra has answered above, Windows Task Scheduler execution is no longer supported since 2017.1 version. So the only option for Unattended without Orchestrator is to run the process manually and then lock the screen.
You already said that it works to run the Unattended Robot in uiautomation process if Simulate type is checked. If Simulate type is not checked it with throw an error (because as stated in the Activities user guide, Simulate type/click option is for background automation - that means that it interacts in the background and you as a user can do other things in the meantime, without losing the mouse/keyboard control, even if it means locking the screen).
Thanks for reply， I know uipath do not support the window scheduler anymore. I just care about run the task and locked the screen ， I think maybe i misunstand about runing from unattended bot when the screen is locked.
I thought if i buy the unattended bot， then we could locked the screen ，and the bot will still run，but according to you said. even if i buy the orchestrator， I just also could run the background activity when the screen is locked？
if the answer is yes，how about catch a picture？ click a picture？ ocr？ I think a lots of activity can t run under the locked screen？ i think it s unreasonable.
I see the high density mode，we can run many bot at the sametime？ is that also could run the background activities？
but @Gabriel_Tatug told me ， with orchestrator and the unattended bot，uipath will create a session the bot，though the screen is locked. the bot still cant run in its own waysession and we dont need to check the simulate type and can use those activities interacted with the interface，like click picture？
We are using the community 2019.1 + Enterprise 2019.1
I can able test the scenario:- Keeping the screen unlocked, scheduled via windows task scheduler, so my questions are,
Once I move to production(deploy),
If I keep prod machine unlocked and schedule using windows scheduler, will it work? (Because in prod we will be having Enterprise, and I’m testing using community does it vary?)
When you said no longer supported, is it the technical support from uipath team or functionality support in uirobot.exe and windows scheduler?