Auto-login support for Bot agent
Use auto-login to automatically log on to a device, run a scheduled automation, and restore the device to its original locked or logged off state after running the automation.
- When an automation is stopped or paused either from the Control Room or device. This ensure that the security of the
machine is not compromised when an automation is paused or
stopped.Note: When the automation resumes, it continues to run in the background on the locked device.
- When an automation encounters an error during execution.
Auto-login support: operating system
Identify the operating system support specific to auto-login on Bot agent devices.
The following scenarios are applicable and supported on local Windows 10 device and virtual machines only:
|1||No user session established (user is not logged in)|
|2||User session established|
|3||User has logged in but locked the screen|
|4||A different user (not the device login user used for deployment) is logged in|
|5||A different user is logged in and locked the screen|
|6||Fast user switching|
The following scenarios are applicable and supported on Windows Server 2019, Windows Server 2016 R2, Windows Server 2012 R2, Windows 10, 8, and 7:
|1||No active RDP session|
|2||User has active RDP session|
|3||User's RDP session is disconnected|
|4||User's RDP session is locked|
|5||Another user has active RDP session|
|6||Another user has a disconnected session|
|7||Another user has an active session and locked|
Auto-login support: operating system with cloud platform
The following table identifies the support specific to auto-login on Bot agent devices for operating system across cloud platforms:
|SID#||Scenario||Windows 2019 - AWS||Windows 2016 R2 - AWS||Windows 2012 R2 - AWS||Windows 10 AWS||Windows 10 Azure (Enterprise)||Windows 10 VMWare (ESXi 6.7 and Horizon)||Windows 10 Citrix|
|1||No active RDP session||Supported||Supported||Supported||Supported||Supported||Supported||Supported|
|2||User has active RDP session||Supported||Supported||Supported||Supported||Supported||Supported||Supported|
|3||User's RDP session is disconnected||Supported||Supported||Supported||Supported||Supported||Supported||Supported|
|4||User's RDP session is locked||Supported||Supported||Supported||Supported||Supported||Supported||Supported|
|5||Another user has active RDP session||Supported||Supported||Supported||Supported||Supported||Supported||Supported|
|6||Another user has a disconnected session||Supported||Supported||Supported||Supported||Supported||Supported||Supported|
|7||Another user has an active session and locked||Supported||Supported||Supported||Supported||Supported||Supported||Supported|
Additional notes on auto-login:
- Auto-login is only supported on 64-bit operating systems.
- Auto-login is unable to sign-out the root admin session, when trying with scenarios that involve two different auto-login users. Remember to log out of the admin user account before deploying a bot.
- For scenarios 4, 5, and 6 in the above tables, the active user is logged off and a new session created with device credentials for deploying the bot.
- If auto-login fails, configure the Local Security Policy
settings. For example, in Windows, select . Enable the Interactive logon:
Do not require CTRL+ALT+DEL option.Recommendation: Enable the Interactive logon: Do not require CTRL+ALT+DEL option to ensure your device is able to bypass the screen to create a user session.
When you deploy a bot from the Control Room on a device, Bot agent receives the deployment and creates an interactive user session for deployment. If the option is disabled, the Bot agent will not be able to bypass the screen to create a user session. Therefore, we recommend you enable this option.