Configure auto-login settings on Windows device - Configure auto-login settings in the Control Room to either create user sessions or reuse existing user sessions to reduce the bot startup time.

Automation 360

Configure auto-login settings in the Control Room to either create user sessions or reuse existing user sessions to reduce the bot startup time.

Before you begin

Ensure that you are logged in to the Control Room as the administrator.

About this task

Auto-login enables you to deploy a bot for unattended Bot Runners after automatically logging on to a machine and restoring the machine to its original locked/unlocked state after completing the deployment.
Note: The Run as user device credentials are used for Auto-login.

Configure auto-login settings to either create new user sessions or reuse existing sessions in the following scenarios:

  • Before deploying a bot, some applications are kept running to accommodate a delay in the application launch.
  • For a Windows based device, Active Directory policy updates are pushed after a user logs in, changes in the automation environment might affect bot execution.
  • Logging off from temporary or non-persistent devices stops bot execution.
  • You can reuse existing user sessions when your company's IT policy prevents you from providing device user password for auto-login credentials.
  • To bypass legal disclaimers on RDP-based deployments.

Procedure

  1. Navigate to Administration > Settings > Devices.
  2. Choose how to run bots on user sessions by selecting one of the following options:
    • Always create a new session

      Select this option for desktop deployments where it is possible to create user sessions on devices.

    • Reuse an existing session
      Recommendation: Select this option for auto-login settings in the Control Room to use event triggers on unattended Bot Runners and to run bots when a device is locked or is in a disconnected state (such as RDP).

      Available options to lock or unlock the session are:

      • An existing locked session
      • An existing unlocked session
      • A disconnected session
      • Allow users to change these settings for each device

      Use this option for deployments on devices where it is not possible to create user sessions.

      Note: When you use the Reuse an existing session option, ensure user sessions are available. If there is no existing user session, triggers and bot deployments will fail.
    • Reuse an existing session, if available

      Use this option if you must create a new session or reuse an existing session. If a session does not exist, create a new session and leave it unlocked for next user session after bots complete their run from the following:

      • A new session
      • An existing locked session
      • An existing unlocked session
      • A disconnected session
  3. Select one of the following options for the new session when the automation completes:
    • Log off
    • Leave the session unlocked
    • Lock the session
    Similarly, you can select the options for an existing locked session, an existing unlocked session, and a disconnected session
  4. Optional: Select one of the following options if you want to allow or restrict users from changing these settings individually for each device:
    • Allow changes
    • Do not allow changes

      Is the default setting and disables the user-level auto-login settings for user sessions.

  5. Click Save changes.