Auto Logon

The “Auto Logon” feature in RobilityRunner is designed to enhance automation efficiency by enabling a robot to automatically log in to a Windows system when it has been signed out or locked. This feature plays a critical role in scenarios where automation needs to function independently of human intervention, such as in unattended automation processes.

In environments where multiple robots share a single system or when systems are configured to log off users after a period of inactivity, the Auto Logon feature ensures that the robot can quickly regain access and resume its operations without manual input. Additionally, this functionality is particularly valuable after system restarts, where the login screen would otherwise prevent the robot from continuing its tasks.

Pre-requisites

1. The workflow execution will only commence once the “Auto Logon” feature has successfully unlocked the machine.
2. Remote Desktop Protocol (RDP) must be enabled on the machine for the robot to connect remotely. Enabling RDP allows users or robots to access the system from another machine, making it crucial for remote automation scenarios.
3. The username associated with the machine connection must be part of a user group (such as the “Remote Desktop Users” group) that has the necessary permissions to use RDP. Without this, even if RDP is enabled, the robot will not be able to auto log in remotely.
4. Robility Runner supports multi-user auto logon on a single machine; however, it allows only one active session per user at a time. If a VM or machine is configured with multiple sessions for the same user, auto logon or auto unlock will not function.

Points to note

1. The Resolution settings will apply exclusively to “Unattended and High-density Runner.”
2. This option is not supported for Attended robots.
3. After configuring the settings and initiating the Run process, if the resource is at logged off state, the changes will be reflected upon auto-login functionality.
4. If the machine is already in at unlocked state, initiating the robot won’t execute the specified resolution changes.
5. The specified resolution changes will be executed only when an auto-login functionality is applied or when the manual unlock action is performed in the machine. Click here to refer the Resolution Settings.
6. The user session must be active while executing the bot.  

Limitations

1. If the credentials provided are incorrect, the Auto Logon process will continue attempting to log in until manual intervention is required to unlock the virtual machine with the correct credentials.
2. The Auto Logon feature is not supported with the Attended robot license type.

How to set up the robot with credentials? 

1. Navigate to the Robility Manager.
2. Select the type of license you need: either “Unattended” or “High-density” robot.
3. Select the “Resources” menu to add the machine that will be used for provisioning and executing the workflow.
4. Select the type of license you need: either “Unattended” or “High-density” robot.
5. Next, go to the “Projects” menu and select the project to which you want to provision the machine for the workflow.
6. Go to the “Deploy Robots” menu and click on “Add” to provision the machine.
7. Select the same license type that you chose for the machine.
8. Choose the “Resource Name” you added, where the workflow will be executed.
9. Select the desired solution for execution.
10. Enter the “Username and Password” for the machine to log in via RobilityRunner.
11. Click on the save button. Now, the license key will be created/ available for the runner connection.