---
locale: "en"
updated_at: "2025-10-27T11:19:20.605Z"
canonical: "https://www.isdecisions.com/en/userlock/docs/guides/installation/advanced/beta-testing-procedure"
---

# Beta Testing Procedure for UserLock

How to install and test the latest features.

## Overview

UserLock beta versions allow administrators to validate new features, improvements, and fixes before public release.

Following the steps below ensures a smooth beta experience and meaningful feedback for improving the final version.

## Prerequisites

Before starting, make sure that:

- You have a **test environment** similar to your production setup to avoid service disruption.
- The test machine **meets the UserLock system requirements** (see [Requirements](/userlock/docs/getting-started/requirements)).
- If you install in production (not recommended):
  - Ensure that [protected zones do not overlap](/userlock/docs/support/troubleshooting/common-issues#conflicting-installation-detected) with any existing UserLock installation.
  - Inform another team member that the **beta version is deployed** on the network and share this guide.
  - **Plan installation during support hours** to receive assistance if needed.

## About beta versions

Beta builds behave like standard versions when a valid license key is registered.

Otherwise:

- **No license key** is required.
- **Expiration date:** Beta versions stop working after a predefined date.
  - If the UserLock service restarts after expiration, startup will be cancelled.
  - If the service remains running, protection and restrictions will no longer apply.

## Download and install the beta version

1. **Download** the latest UserLock beta from the [download page](https://www.isdecisions.com/en/userlock/download).
2. Follow the standard setup process described in [Quick start with UserLock](/userlock/docs/getting-started/quick-start).
3. During installation, select **Primary Server** in the **Configuration Wizard**.
4. **Do not install** the UserLock Desktop Agent on the beta server itself.
This avoids being locked out in case of incorrect access policy configuration or test errors.

## Testing Features

We recommend performing your tests **during IS Decisions support hours** so our team can assist if needed.

1. **Test the new features** or fixes listed in the beta release notes.
2. **Verify the user experience:** Check that the interface is intuitive and stable.
3. **Validate integrations:** Ensure compatibility with your environment (VPN, IIS, etc.).
4. **Monitor system performance** and confirm that UserLock behaves as expected.

## Reporting issues

If you encounter any issue:

1. **Enable verbose logging** (see [how to enable verbose mode on agent logs](/userlock/docs/support/faq/agents)) to capture detailed information.
2. Include in your report:
  - Steps to reproduce the issue
  - Screenshots or logs
  - Expected vs. actual behavior

**Contact IS Decisions support:**

- 📩 [Web support form](https://www.isdecisions.com/en/support)
- ✉ [support@isdecisions.com](mailto:support@isdecisions.com)
- ☎ +33 559 414 220

Support is available **Monday–Friday, 9:00–12:30 and 14:00–18:00 (CET / UTC+1)**.

## Providing feedback

After completing your tests:

- **Report your findings**: successes, issues, and anomalies.
- **Suggest improvements** or new features.
- **Comment on usability**: clarity, performance, and ease of use.

Your input directly helps improve the final version of UserLock.

## Finalizing the beta test

Once the public release is available:

1. **Upgrade your test or production environment** to the final version.
→ See [Upgrade procedure](/userlock/docs/guides/installation/upgrade-procedure).
2. **Remove the beta version** if it is no longer needed.
3. Share your final observations with the IS Decisions team.