Beta Testing Procedure for UserLock

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.

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).

• If you install in production (not recommended):

  • Ensure that protected zones do not overlap 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.

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.

1. Download the latest UserLock beta from the download page.

2. Follow the standard setup process described in Quick start with UserLock.

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.

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.

If you encounter any issue:

1. Enable verbose logging (see how to enable verbose mode on agent logs) 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

• ✉️ support@isdecisions.com

• ☎️ +33 559 414 220

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

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.

Once the public release is available:

1. Upgrade your test or production environment to the final version.
   → See Upgrade procedure.

2. Remove the beta version if it is no longer needed.

3. Share your final observations with the IS Decisions team.