Verify your setup
After installing UserLock, deploying your first agent, and configuring an access policy, the final step is to verify that everything works as expected. This ensures your deployment is ready to monitor sessions, enforce rules, and generate reports.
Useful resources
Log on to the workstation where you deployed the agent with an account not restricted by any access policy.
In the UserLock console, go to Activity ▸ Active sessions.
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.
If no activity is displayed, it may indicate an issue with the agent installation.
In the UserLock console, go to Environment ▸ Machines.
Search for the machine and click on its name to open the machine dashboard.
Click on the Actions button, then on Check the agent status.
A message will appear on the bottom right corner to inform you about the agent status.
If the agent is not correctly installed, refer to the Troubleshooting agent deployment page.
Next, verify that the access policy you configured is applied correctly.
If you have followed our machine restriction example in the previous page:
Log on to the protected machine with the user account you configured in your test policy.
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.
Finally, open the Reporting section in the UserLock console.
Select the Denied logons report.
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.
🎉️ 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 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 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 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 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 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 (license status, availability problems, etc.) to be informed immediately if something requires attention.Move to a production database
Connect UserLock to a production database to ensure long-term data retention, improved performance, and secure storage of audit logs.