LM-X License Manager version 4.9.21 includes the enhancements and fixes detailed below. The changes in this release were made primarily in response to customer feedback. For more information about how we incorporate customer feedback into our development process, see Customer-driven development.

Due to improvements to 64-bit support in this release, Pay-Per-Use databases created using a previous version of the LM-X license server no longer work in v4.9.21 and newer.

You can still use lmxendutil from prior versions for verifying databases created prior to v4.9.21; however, the OS version (32-bit or 64-bit) of lmxendutil and the database must match. That is, you must use a 32-bit version of lmxendutil with a database generated by a 32-bit license server, and a 64-bit version of lmxendutil with a database generated by a 64-bit database.

Databases created by LM-X v4.9.21 or newer should be verified by the new lmxendutil. We also recommend that you specify a new file for the database, since the database that was created by the older version and is still being used in LM-X v4.9.21 and newer won't be verified by lmxendutil.


Enhancements

LM-X v4.9.21 includes the following enhancement.

Issue #Description
LMX-3987

Validation of LM-X vendor names has been made stricter.

Fixes

LM-X v4.9.21 includes the following fixes.

Issue #Description

LMX-3953

The LM-X installer no longer requires root privileges.

LMX-3965HyperV detection no longer returns false positives.
LMX-3986Pay-per-use database created on a 32-bit machine can now be used on a 64-bit machine. 
LMX-4007Fixed issues with replacing licenses. License replace string is now part of license key.