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.

The Run as user device credentials are used for Auto-login. Auto-login restores a device to its original state in the following scenarios:

Automation was stopped on the Control Room or device.
An error in encountered during bot execution.
When the automation completed successfully.

Auto-login support: operating system

Identify the operating system support specific to auto-login on Bot Agent devices. The auto-login process involves several stages and depends on the Bot Agent activity.

The following scenarios are supported on Windows 10 and virtual machines only:


SID#	Scenario
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

For scenarios 4, 5, and 6 in the above table, the active user is logged off and a new session is created with device credentials for deploying the bot.

The following scenarios are applicable and supported on Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 10, 8, and 7:


SID#	Scenario
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

Note: Remote Desktop Protocol (RDP) based deployment on a Virtual Machine (VM) hosted in Amazon Web Services (AWS) workspace is not supported when there is an active user session (no active console session from previous user login).

The following table identifies the support specific to auto-login on Bot Agent devices for operating system across cloud platforms:


SID#	Scenario	Supported OS
1	No active RDP session	Windows 2019 - AWS Windows 2016 R2 - AWS Windows 2012 R2 - AWS Windows 10 AWS Windows 11 (Enterprise) Windows 10 Azure (Enterprise) Windows 10 VMWare (ESXi 6.7 and Horizon) Windows 10 Citrix
2	User has active RDP session	Windows 2019 - AWS Windows 2016 R2 - AWS Windows 2012 R2 - AWS Windows 10 AWS Windows 11 (Enterprise) Windows 10 Azure (Enterprise) Windows 10 VMWare (ESXi 6.7 and Horizon) Windows 10 Citrix
3	User's RDP session is disconnected	Windows 2019 - AWS Windows 2016 R2 - AWS Windows 2012 R2 - AWS Windows 10 AWS Windows 11 (Enterprise) Windows 10 Azure (Enterprise) Windows 10 VMWare (ESXi 6.7 and Horizon) Windows 10 Citrix
4	User's RDP session is locked	Windows 2019 - AWS Windows 2016 R2 - AWS Windows 2012 R2 - AWS Windows 10 AWS Windows 11 (Enterprise) Windows 10 Azure (Enterprise) Windows 10 VMWare (ESXi 6.7 and Horizon) Windows 10 Citrix
5	Another user has active RDP session	Windows 2019 - AWS Windows 2016 R2 - AWS Windows 2012 R2 - AWS Windows 10 AWS Windows 11 (Enterprise) Windows 10 Azure (Enterprise) Windows 10 VMWare (ESXi 6.7 and Horizon) Windows 10 Citrix
6	Another user has a disconnected session	Windows 2019 - AWS Windows 2016 R2 - AWS Windows 2012 R2 - AWS Windows 10 AWS Windows 11 (Enterprise) Windows 10 Azure (Enterprise) Windows 10 VMWare (ESXi 6.7 and Horizon) Windows 10 Citrix
7	Another user has an active session and locked	Windows 2019 - AWS Windows 2016 R2 - AWS Windows 2012 R2 - AWS Windows 10 AWS Windows 11 (Enterprise) Windows 10 Azure (Enterprise) Windows 10 VMWare (ESXi 6.7 and Horizon) Windows 10 Citrix

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.

Automation 360

Auto Login support for Bot Agent