---
version: "2026"
language: "en"
---
# Agent FAQ

## What Windows authentication types does the Remote Agent support?

Leapwork supports three Windows authentication methods to connect to a VM running the Remote Agent service:

* **Windows login:** Requires a Windows username and password. Use `whoami` in Command Prompt to find the username. Add a **Login** block in your automation flow to simulate logging in.

* **Windows login -- Auto:** Automatically logs in with credentials set in the Agent Connection settings. No **Login** block is needed in your flow.

* **Password:** Uses the password set during agent installation. No username required.

  ![image-20250911-084848.png](https://docs.leapwork.com/__attachments/a_33c390ed303ea87966267afdfcb16e1446667ab03914226d39ef97033d4313a6/image-20250911-084848.png?cb=e2efc1873e8c063b9f96e0bd4933620f)

All three methods work on VMs without an active user session, starting from Windows 7 SP1. This simplifies automation on virtual machines and SSO testing.  
**Note:**This feature uses Windows' built-in credential provider and does not bypass any security layers.

**Granting local log-in rights to a non-admin user**

If a non-admin user needs access to the agent machine, grant them **Allow log on locally** rights:

1. Open the **Run** dialog (`Windows + R`), type `gpedit.msc`, and press Enter.

2. Navigate to:

   `Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment`

   ![image-20250911-085438.png](https://docs.leapwork.com/__attachments/a_fc7bdfe3578b15f0fab9830f8da79cbce06e79fc71f326435d7b4c9c795528ce/image-20250911-085438.png?cb=4a45f2b178f8437fe0b188bcba257776)
3. Right-click **Allow log on locally** and select **Properties** .

   ![image-20250911-085510.png](https://docs.leapwork.com/__attachments/a_918a879c6f25180bb8e61c466a060dbb659d41e8c3e6821860f40accca65d8f0/image-20250911-085510.png?cb=48b39aa1307ef3803c6320e874d9e844)
4. Click **Add User or Group** , add the user, and apply the changes.

   ![image-20250911-085549.png](https://docs.leapwork.com/__attachments/a_7fbba9efcc06f52e102528c19b1f155d398fb65cdfbbb916aca71fe4220f2500/image-20250911-085549.png?cb=30468b0c9c26215236ee1123b42eb063)
5. Restart the machine.

*** ** * ** ***

## **How do I run test cases on a remote computer?**

To run tests remotely, install the **Leapwork Agent** on one or more dedicated machines. This offloads test execution from your local computer and allows for parallel test runs across multiple machines.

* Before installing, review the [Leapwork Architecture Overview](https://docs.leapwork.com/leapwork-flow/latest/what-is-leapwork/architecture-overview.md). Then follow the steps in [Agent Installation on Windows](https://leapworkdocumentation.atlassian.net/wiki/pages/resumedraft.action?draftId=221839373&draftShareId=33963596-cf74-4379-bbd9-63b0903ed6bd&atlOrigin=eyJpIjoiYWNkNTU4NzY2NGI2NDk2N2ExNDA0MTY4YzEzY2Q1OTciLCJwIjoiYyJ9).

  After installation, register the agent in the **Environment** section so the Controller can manage it.

*** ** * ** ***

## **How do I set up Selenium Grid (general)?**

Selenium Grid lets you run tests in parallel across different browsers and operating systems, speeding up execution and supporting multi-browser environments.

1. **Download and Prepare Files**

* Download the latest **Selenium Server JAR** from [Selenium HQ](http://www.seleniumhq.org/download/).

* Download and extract **Grid_Setup.zip** , and move the folder to `C:\Grid Setup`.

* Copy the downloaded `.jar` file into the `C:\Grid Setup` folder.

2. **Set Up the Hub**

* Edit `hub.bat` to ensure the `.jar` filename matches the one you downloaded.

  ![image-20250911-092230.png](https://docs.leapwork.com/__attachments/a_4aa10f26a82b50bbd6c4caf78e478ee78207ad94ebda3c28977131395cea2705/image-20250911-092230.png?cb=8d300807793263a7b44e417e0f25e1f3)
* The hub uses `hubconfig.json` to load default configurations.

  ![image-20250911-092306.png](https://docs.leapwork.com/__attachments/a_acf2ad823d852e621d72646583bab74fc9436ba0d62e814436d45a8669c32a97/image-20250911-092306.png?cb=4ae5aa067c0aeb021f8211e77e83600b)
* Run `hub.bat`. Verify the hub is running by visiting:

  `http://localhost:4444/grid/console`

  ![image-20250911-092326.png](https://docs.leapwork.com/__attachments/a_9ad086742c9370570768dd3bd4b7dff39f8e63387d6d9c6342b6bd957d13cfa8/image-20250911-092326.png?cb=e3fdea4d7c3e7a345e4447d846fcb9dd)

3. **Set Up the Node**

* You can use the same or a separate machine.

* Update driver files in `C:\Grid Setup` with the latest versions for Chrome, Firefox, Edge, and IE.

  ![image-20250911-092552.png](https://docs.leapwork.com/__attachments/a_fdaeb4f097fa980e18426f3e5d35c753bf5b47ee43f3ebf2306c381746833878/image-20250911-092552.png?cb=e3739343f0f5f516ea0990589f6c46fb)
* Edit `node.json` to define:

  * `"browserName"` (e.g. `"chrome"`)

  * `"maxInstances"`

  * `"hub"` URL (use `localhost:4444` or hub IP if remote)

    ![image-20250911-092615.png](/__attachments/a_5aa4d0a42cf66ddc084042b50903ee38cc6d45ebeb85191997ece038bb868573/image-20250911-092615.png?cb=47eaf02b4ccf05d07e611a6b9d1ddf68)
* Edit `node.bat` to reflect the correct `.jar` file name.

  ![image-20250911-092654.png](https://docs.leapwork.com/__attachments/a_d06b0ce0dc421078c542feeb3f725bde4759b6a2a12f4d6ccca3f4c41fe095d9/image-20250911-092654.png?cb=0307a82f67ae2820722dcfd1a339c1c4)
* Run `node.bat`. Once the node connects, it appears in the Grid Console.

  ![image-20250911-092717.png](https://docs.leapwork.com/__attachments/a_0522222ecff5b1a4c6084683565f0e888521b4c16736f655ba856104fd12c6f9/image-20250911-092717.png?cb=f6c266e3294a2a06434ed3e983ca9d85)

4. **Connect Leapwork**

Configure Leapwork to run tests on your grid using the integration article. You can scale by adding more nodes on different machines.

*** ** * ** ***

## **How do I configure Selenium Grid on macOS (Safari/Chrome/Firefox)?**

Selenium Grid allows you to run tests in parallel across multiple browsers and OSs, helping reduce test execution time.

1. **Download Required Files**

* Download **Selenium Server JAR** from [Selenium HQ](http://www.seleniumhq.org/download/).

* Download latest **ChromeDriver** and **GeckoDriver** (for Firefox).

* Safari's driver is pre-installed at `/usr/bin/safaridriver` (macOS 10+).

2. **Driver Configuration**

Move the drivers to `/usr/local/bin`:

    mv chromedriver /usr/local/bin  
    mv geckodriver /usr/local/bin  

3. **Safari Setup**

* Enable **Develop menu** via Safari Preferences \> Advanced.

* From the Develop menu, enable **Allow Remote Automation**.

* Run once to authorise:

    safaridriver --enable

4. **Set Up Selenium Grid**

* Download and extract **SeleniumGrid.zip** to your Desktop.

* Rename your `.jar` file to `selenium-server-standalone.jar` and place it in the folder.

* Make the script executable:

    chmod u+x ~/Desktop/Selenium\ Grid/gridSetup.command

* Double-click `gridSetup.command` to launch both Hub and Node.

Verify the grid at: `http://localhost:4444/grid/console`

5. **Connect to Leapwork**

Once the grid is running, configure Leapwork to run your tests using the related setup article.

*** ** * ** ***

## **How do I connect Leapwork with the Gridlastic cloud agent (Selenium 4)?**

Leapwork integrates with cloud providers like **Gridlastic**, which offers on-demand Selenium Grid infrastructure. This allows you to run Leapwork flows across different devices, browsers, and operating systems.

Follow these steps to connect Leapwork:

1. Log in to your **Gridlastic dashboard** .

   ![image-20250911-110919.png](https://docs.leapwork.com/__attachments/a_7abe4658fcd0824d1bed78bc2191cb412f730ab86f84fdc6cab9c0062868231f/image-20250911-110919.png?cb=a1914f840ba4bc07c59d6a34eb629cb1)
2. Go to **Grid Configurations** in the left panel.

3. From the **Selenium Version** dropdown, select **4.7.0** .

   ![image-20250911-110948.png](https://docs.leapwork.com/__attachments/a_faabffc741ed856c4865b37797741916c57334ee28046db90c1f1977131cb60b/image-20250911-110948.png?cb=3f114aa2fc2c672c4ad003a7f5f24cd2)
4. Click **Launch Grid**. The grid will generate:

   * Subdomain

   * Username

   * Password / Access Key

5. In Leapwork Agent settings, create a new [Gridlastic agent](https://leapworkdocumentation.atlassian.net/wiki/spaces/ARM/pages/edit-v2/221839373#GridLastic)using these details.

*** ** * ** ***

## **How do I change the Agent port?**

By default, the Leapwork Agent uses port **6777**. If another application is using it, the Agent service may fail to start. You can manually change the port without reinstalling:

1. **Stop the Agent service**

   * Press **Win+R** , type `services.msc`, and press **Enter**.

   * Find **Leapwork Agent** , right-click, and select **Stop** .

     ![image-20250911-114205.png](/__attachments/a_2206b2210126b8f4518b6c9eb6fb86a0426d6685269e977191f7fc725daf0b16/image-20250911-114205.png?cb=558e5a831e6bec66dff1aa59c72c4f32)
2. **Edit the configuration**

   * Go to `C:\Program Files\Leapwork\Agent`.

   * Open **agent.config** as Administrator.

   * Change the value of **AgentPort** , save, and close.

     ![image-20250911-114328.png](/__attachments/a_42dd25740cc041df8afcd6434377f0144ce908ddb921ce049f1cf5dfe23adbdf/image-20250911-114328.png?cb=eb701cb17506422271f767998a9d7bf4)
3. **Restart the Agent service**

   * Return to **Services** , right-click **Leapwork Agent** , and select **Start**.

4. **Update your firewall**

   * Allow inbound traffic on the new TCP port.

5. **Test connection**

   * Use **Leapwork Flow** to confirm the Agent is reachable.

     ![image-20250911-114406.png](/__attachments/a_274d3c2a2a3be61a1965e9ce1a78c493e29ed357789b94747c12d48e22ecba5a/image-20250911-114406.png?cb=174f3a36d7487196c3f4eb2c839395c4)

*** ** * ** ***

## **How can I keep the Agent's display resolution consistent?**

Running tests at a fixed resolution can fail if the Agent's display settings change. To keep resolution stable, follow these practices:

1. **Use a dedicated service account**

   * Avoid connecting multiple users to the same Agent.

   * Remote desktop sessions can change resolution or disrupt tests if closed mid-run.

2. **Align resolution in Leapwork Flow**

   * In **Environment settings** , ensure all users configure the same resolution (Native or a chosen fixed value).

     ![image-20250911-121640.png](/__attachments/a_51b156171c93c89943f9cd765db3dfb55e2913a3f31f35e766855b77cc7f61b9/image-20250911-121640.png?cb=b6c6879f8a8a8d4365dbe33eef0696af)
3. **Set resolution manually on the Agent machine**

   * From Leapwork Environments, keep **Screen Resolution** as **Native** , then click **Test connection** .

     ![image-20250911-121434.png](/__attachments/a_e373a768fbec502bc4d7622f50aca04968f662ac0758eba264f53dff71922e6b/image-20250911-121434.png?cb=bdeb54b1f03f426a1b7491dfeb90e30e)
   * On the Agent desktop:

     * Right-click → **Display settings** → **Advanced display settings**.

     * Select the required resolution → **Apply** → **Confirm** .

       ![image-20250911-121552.png](/__attachments/a_9c93ea44b0ab96e5a4e178a218ec289f4aed5a200f0ec9bc79925afa37cd0016/image-20250911-121552.png?cb=ec0f2a2a4d3b49f66e4b73e76c67c334)

By following these steps and keeping accounts and configurations consistent, the Agent will run tests at a stable resolution.

*** ** * ** ***

## **How do I prevent the Agent machine from logging out or sleeping?**

By default, Windows locks or sleeps after a set time. To keep the Agent active, follow these two steps:

1. **Disable Power \& Sleep Settings**

Ensure the machine never locks or sleeps automatically:
Sleep settings on different OS  
* **Windows 10**

  * Right-click the Start menu → Power Options.

  * For a local desktop: set all Sleep options to Never.

  * For a Windows 10 VM: set all Power \& Sleep options to Never.

* **Windows 8**

  * Right-click the Start menu → Power Options.

  * Select Choose when to turn off the display.

  * For a local desktop: set Put the computer to sleep to Never.

  * For a VM: set both Turn off the display and Put the computer to sleep to Never.

  * Click Save changes.

* **Windows 7**

  * Start menu → Control Panel → System and Security → Power Options.

  * Next to the selected plan, click Change plan settings.

  * Set Turn off the display and Put the computer to sleep to Never.

  * Confirm with OK → Save changes.

* **Windows Server 2008 \& 2012**

  * Start menu → Control Panel → System and Security → Power Options.

  * On Choose or Customize a power plan, select Change plan settings.

  * Set Turn off the display and Put the computer to sleep to Never.

  * Click OK → Save changes.

If your organisation restricts these changes, host the Agent on a **VM** and adjust settings there.

2. **Update Agent Configuration**

Modify the Agent config file to keep the display active:

1. Stop **Leapwork Agent** from `services.msc`.

2. Open `C:\Program Files\Leapwork\Agent\agent.config` in Notepad (as Administrator).

3. Add:

       "KeepDisplayActive": true,

   ![image-20250911-122648.png](https://docs.leapwork.com/__attachments/a_c657f817ae8232f2dba76b4b10a7f20db53a5f9a97701f7163f32e0ac7a15610/image-20250911-122648.png?cb=cec6d10b8f062f97938ba02df9c001fc)
4. Save the file and restart the Agent service.

5. In **Leapwork Flow**, refresh Controller settings to apply changes.

With these adjustments, the Agent machine will stay awake and maintain its session for test execution.

*** ** * ** ***

## **Can Leapwork log in/out when the Agent's screen is locked?**

Leapwork supports two ways to log in and out of a locked Agent machine:

1. **Windows Credential Provider**

* Leapwork can log in on behalf of the user and support SSO testing.

* Add **Login** , **Logout** , or **Lock** blocks to your flows. For example, use a **Login** block at the start and a **Logout** block at the end of automation.

  ![image-20250911-133300.png](https://docs.leapwork.com/__attachments/a_dd4d7d5c269151d8a27481c72c8eb7d391c2ab9c881fa4e13591c83a8a4a3c0d/image-20250911-133300.png?cb=c8f3c7351ddecef25bae8ffdaa87be19)
* Agent settings let you log in automatically or manually with a Windows account, and optionally lock the session after disconnect.

* **Preconditions**:

  * Install the latest Leapwork with **Windows Credential Provider**.

  * Select **Windows login** during Agent installation.

    ![image-20250911-133349.png](/__attachments/a_23096181dedede047d2f8441f3c8d3d163f3a5328c306976cd0b5ae0f6f99b81/image-20250911-133349.png?cb=11293eb02e4b8fa6bcbdf5312be42ed5)
  * No one should be connected via Remote Desktop.

  * Restart the machine after installation.

* Works from **Windows 7 SP1 onwards**, even after reboot, without prior sessions.

2. **Custom Blocks with Images and Text**

* Create a **Custom Remote Login Block**:

  1. Lock the Agent machine.

  2. Capture a static element of the lock screen (e.g. *Press Ctrl+Alt+Delete*).

  3. Use a **Type Text** block to send `Ctrl+Alt+Delete`.

  4. Use **Find Image** + **Click Position** to select the user account.

  5. Type password and press **Enter** to log in.

     ![image-20250911-133412.png](/__attachments/a_63e5cc9c5de1529465092cd300e6165db088dab65b300e6c8c8a6e1d16ef5496/image-20250911-133412.png?cb=9aea6a1c99f2bb1033e6033ad58c5cf6)
* Add a similar **Logout flow** as the final step or case in your run list.

* The scheduler runs cases in order (top to bottom); reorder by drag and drop.

*** ** * ** ***

## **Why is the Preview environment empty over RDP on Windows 7/Server 2008 R2?**

On Windows 7 SP1 and Windows Server 2008 R2, limitations in desktop duplication technology prevent Leapwork Flow features from working over **Remote Desktop Connection**. As a result, the preview environment appears blank.

* You can still run Leapwork Agent on these systems as a System Under Test, but Leapwork Flow cannot be used via RDP.

* Flow works under these conditions:

  * Windows 7 SP1 / Server 2008 R2 on a physical machine with a physical display.

  * Windows 7 SP1 / Server 2008 R2 with Leapwork Agent only as System Under Test.

  * Windows 8 or later: fully functional, including RDP.

*** ** * ** ***

## **How can we reset the Leapwork Agent password?**

When installing the Leapwork Agent, you're prompted to set a password for configuration security. If you later forget this password, you have three options:

1. Reinstall the Agent component and set a new password during installation.

2. Check Windows Registry (`HKLM\\SOFTWARE\\LEAPWORK → AgentPassword`). If the value is visible (not encrypted), you can retrieve it. If encrypted, this approach won't work.

   ![image-20250915-123149.png](https://docs.leapwork.com/__attachments/a_4477b37bae7eb3b66c15fa18881694bc3caa5ef924b8ef90cde3f817c50c9f7f/image-20250915-123149.png?cb=58025ff6ef15e361cef29ffad3f14446)
3. Clear the password in agent.config:

   * Stop the **LEAPWORK Agent** service.

   * Navigate to `C:\Program Files\LEAPWORK\Agent` and back up *agent.config*.

   * Remove the encrypted value under the `Password` field.

     ![image-20250915-123225.png](/__attachments/a_30edcd7bb66c12d83ab890999804c171a7a0b862e07ff7a64c285e447079fbe4/image-20250915-123225.png?cb=656f0a1640d082f7c6dd2cb02c3693c2)
   * Save, restart the Agent service, then configure in Flow with a blank password.

If none of these work (for example, if the registry value is encrypted), reinstalling is the only supported way to reset the password. For special cases, contact [Priority Support](mailto:prioritysupport@leapwork.com).