---
locale: "en"
updated_at: "2025-10-24T14:34:00.557Z"
canonical: "https://www.isdecisions.com/en/userlock/docs/getting-started/verify-your-setup"
---

# Verify your setup

Checking the configuration, next steps

## 1. Check audit activity

1. Log on to the workstation where you deployed the agent with an account **not restricted by any access policy**.
2. In the UserLock console, go to **Activity** **▸ Active sessions**.
3. You should see an open session appear. This confirms that the workstation agent is **successfully communicating** with the UserLock server and that auditing is operational.

> **Note**
>
> To discover all the details you can monitor in real time, such as session type, location, logon method, and more, see the [Activity reference](/userlock/docs/reference/activity).

#### No session displayed

If no activity is displayed, it may indicate an issue with the agent installation. 

1. In the UserLock console, go to **Environment ▸ Machines**.
2. Search for the machine and click on its name to open the machine dashboard.
3. Click on the **Actions** button, then on **Check the agent status**.
4. A message will appear on the bottom right corner to inform you about the agent status.
5. If the agent is not correctly installed, refer to the [Troubleshooting agent deployment page](/userlock/docs/support/troubleshooting/deployment-errors).

## 2. Test your access policy

Next, verify that the access policy you configured is applied correctly.

If you have followed our **machine restriction example** in the [previous page](/userlock/docs/getting-started/configuration-access-policy):

1. Log on to the protected machine with the user account you configured in your test policy.
2. The logon attempt should be denied.

This confirms that **your access policy is active** and its rules are enforced correctly.

> **Note**
>
> If the test user is still able to log on, and you already verified that the agent is working correctly, then review the rules configured in your access policy.

## 3. Review the denied logons report

1. Finally, open the **Reporting** section in the UserLock console.
2. Select the **Denied logons** report.
3. By default, the report shows all denied logons of the last 7 days. You should see an entry corresponding to the failed test attempt above.

This demonstrates how UserLock not only enforces access policies, but also records them for auditing and compliance purposes. 

Reporting gives you a historical view of all activity. It helps administrators track trends, detect anomalies, and generate compliance-ready audit evidence.

> **Note**
>
> Learn more about the reporting capabilities in the [Reporting reference](/userlock/docs/reference/reporting).

## Next steps

🎉 **You’ve completed the Getting Started guide!**

Your UserLock deployment is now fully operational: enforcing access policies, monitoring sessions in real time, and generating detailed audit-ready reports.

Here are some recommended next steps to strengthen and extend your protection:

- **Implement Multi-Factor Authentication (MFA)**
Secure logons with MFA on workstations, RDP, VPN, SaaS and IIS.
The [MFA implementation guide](/userlock/docs/guides/mfa-implementation/how-to-implement-mfa) explains how to deploy it quickly and includes practical tips and best practices to simplify enrollment and user adoption.
- **Protect users working remotely**
Set up [UserLock Anywhere](/userlock/docs/reference/modules/userlock-anywhere) to extend MFA and access policy enforcement to **remote sessions**, even when users are outside the corporate network or VPN.
- **Control where users connect from**
Use a [Geolocation access policy](/userlock/docs/reference/access-policies/geolocation) to allow logons only from authorized countries and block connections from unexpected or high-risk regions.
- **Limit how users enter the network**
The [Initial access points policy](/userlock/docs/reference/access-policies/initial-access-points) helps reduce the attack surface by restricting the number of machines a user can use to connect — with an option to close previous sessions remotely if needed.
- **Stay informed about denied logons**
Configure an [Alerts & notifications policy](/userlock/docs/reference/access-policies/alerts-and-notifications) to be alerted when UserLock blocks a connection attempt, so you can quickly investigate unusual activity.
- **Monitor service health**
Enable [notifications for UserLock service events](/userlock/docs/reference/server-settings/service#service-notifications) (license status, availability problems, etc.) to be informed immediately if something requires attention.
- **Move to a production database**
Connect UserLock to a [production database](/userlock/docs/guides/database/define-a-production-database) to ensure long-term data retention, improved performance, and secure storage of audit logs.