Support > Forums > OpenBots Server > Cloud Server Orchestrator Schedule - Runner BOT failed to unlock the machine
January 04,2023 at 10:28 AM
Dear Team,
Please note that we've scheduled a process via the cloud server Orchestrator and the high-level overview of the scheduled process is that the BOT logins to a web application and download reports.
We've connect the Agent to the orchestrator and the scheduler is working without any issue. However, we observed that the BOT did not unlock the Runner Machine and once we manually unlocked the machine, the BOT was able to commence the rest of the process where the BOT needs to login to a web application and navigate.
Kindly let us know the way forward of enabling the auto login option for the Runner BOT which would enable to automatically login and lock the screen once a process execution was completed.
Thanks, Thamali Jayaweera.
This forum has 65 topics, 191 replies, and was last updated 9 months ago by Ghouse Shaik
January 11,2023 at 10:08 PM Hi Thamalij,
Once an Agent is connected, it will use the linked Active Directory credentials to create the Remote Desktop session in the locked machine. Please ensure the linked credentials are correct.
As an additional safeguard, you can set your Agent to "Always Create a New Session" in the execution settings. This will ensure a new unattended session is created when a new job starts. Thanks!
You are not authorized to reply, please click here to login and add your reply to this topic.