---
title: "Agents | UserLock FAQ"
description: "Frequently asked questions about UserLock agents."
locale: "en"
updated_at: "2026-06-09T09:31:54.086Z"
canonical: "https://www.isdecisions.com/en/userlock/docs/support/faq/agents"
---

# Agents

Understand what UserLock agents do and how they communicate with the server.

## How can I deploy the UserLock agent?

There are 3 ways to install the agent:

- through UserLock console (manually or automatically),
- thanks to the Microsoft Group Policies Object,
- using a third deployment software solution.

We provide agent Msi packages. Please read the [help guide](/userlock/docs/guides/deploying-agents/desktop-agent#group-policy-deployment) to read more about the different procedures.

## How can I manually uninstall the UserLock agent from a workstation?

Simply follow the [Uninstall the Desktop Agent](/userlock/docs/getting-started/agent/desktop-agent#uninstall-the-agent) section of the Desktop Agent manual installation help page.

## How can I allow an IIS application configured with custom user credentials rather than built-in machine credentials to work correctly with UserLock?

In IIS, the application pool identity of Application Pools is configured by default with **ApplicationPoolIdentity**. It is possible to change this with other built-in accounts (LocalService, LocalSystem, or NetworkService) or a custom account based on user type credentials. If an IIS application's application pool is configured with user type credentials, it will not work properly with UserLock unless you set the UserLock advanced settings [Enforce machine account for NPS and IIS agents](/userlock/docs/server-administration/server-properties/advanced-settings) to false.

**Note**: If an IIS application's application pool is configured with one of the built-in accounts (ApplicationPoolIdentity, LocalService, LocalSystem, or NetworkService), there is no need to change the value of this setting.

## How to enable verbose mode on agent logs?

You can activate the Userlock agent's log verbose mode in 2 different ways:

- **From the Userlock console:**
  1. Open a machine dashboard by clicking on the machine name or by choosing the **View details** action.
  2. Then, in the **Actions** button of the Dashboard menu, select the **Agent log verbose** action.
- **Manually method: **
  1. Run 64-bit PowerShell console with the option **Run as administrator** from the workstation concerned.
  2. Execute the following command:

```powershell
Set-ItemProperty -Force -path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' -Name LogPriority -Value 1
```

## How to update the status of one specific computer in Machines view?

​​​Here is the procedure to update the status of one specific computer in the Machines view. Instead of waiting for the pooling of Machines view to check the status of that computer. 

Note that it is **not recommended** to apply this procedure to a large​ list of computers, because it will take as much, if not more time as the pooling of Agent Distribution.

1. Log on to the UserLock server with a user account which has both administrative rights on the UserLock server and [UserLock administrative rights](/userlock/docs/server-administration/server-properties/security).
2. Click on the 3 little dots at the top right of the Userlock console, then click on **Userlock command tool **(not available from the web console).
3. Run the following command: `Deployer Check [WORKSTATIONNAME]`
  - Replace WORKSTATIONNAME with the name of the workstation as displayed in the UserLock Console. Only use uppercase characters.

![](https://a.storyblok.com/f/122374/677x343/e06bd50c8a/ultermdeployercheck.png)

The answer should be “OK: 1”. If so, this will refresh the status on the UserLock console for this computer.

Refresh the Machines view and verify that the status has been updated for that workstation.​