This page details the support policy for LM-X License Manager, including a list of currently supported versions, the support period for security maintenance, and related compatibility expectations.
Versioning and support overview
LM-X v6.x is the currently supported major version. Note the following regarding versioning and support for LM-X:
- LM-X v6.x is supported for security maintenance
- Older supported LM-X versions receive security fixes only
- LM-X v6.x support ends 12 months after LM-X v7.0 is officially released
- After that date, LM-X v6.x will be unsupported even if some versions remain operational in existing deployments
Customers are expected to use the latest available LM-X release within the supported major version whenever possible. Earlier releases in the same major version may remain supported, but they are not the recommended target for new deployments or long-term operation.
Compatibility rules
X-Formation makes every effort to ensure that existing deployed software continues to work with newer LM-X license servers, and that older license files can be read by newer license servers.
LM-X is designed for backward compatibility by ensuring:
- Older LM-X license files can be read by newer LM-X license servers
- Older LM-X clients can work with newer LM-X license servers
- Existing deployed applications continue to work when LM-X is upgraded within the supported major version
LM-X does not support future compatibility; therefore:
- A newer LM-X client is not expected to work with an older LM-X license server
- A newer LM-X license file is not expected to work with an older LM-X deployment
When upgrading LM-X, note the following:
- Existing deployed client applications and existing license files are expected to continue working with newer LM-X versions
- New license files cannot be used by older LM-X applications or older LM-X license servers
- If floating licenses are distributed, end users may also need to upgrade their LM-X License Server to use newer LM-X licenses
- External redistributables used by LM-X integrations, such as Java, .NET, or similar bindings, must also be updated to the corresponding newer versions when required
X-Formation may limit or discontinue compatibility in cases where maintaining compatibility would compromise the security of protected applications, deployed systems, or supported LM-X releases.
Currently supported versions
The following table shows the LM-X versions currently supported as stated in this policy.
| Version | Release date | Status | Support note |
|---|---|---|---|
| 6.1 | 2026-05-21 | Supported | Latest released version in the currently supported major version |
| 6.0.7 | 2026-02-20 | Supported | Supported within LM-X v6.x |
| 6.0.6 | 2025-12-10 | Supported | Supported within LM-X v6.x |
| 6.0.5 | 2025-10-08 | Supported | Supported within LM-X v6.x |
| 6.0.4 | 2025-09-11 | Supported | Supported within LM-X v6.x |
| 6.0.3 | 2025-07-07 | Supported | Supported within LM-X v6.x |
| 6.0.2 | 2025-06-10 | Supported | Supported within LM-X v6.x |
| 6.0.1 | 2025-05-29 | Supported | Supported within LM-X v6.x |
| 6.0 | 2025-04-25 | Supported | Supported within LM-X v6.x |
| 5.6.4 | 2024-10-23 | Not supported | Unsupported as of 2026-04-25 |
Once LM-X v6.x reaches the end of its support period, the versions in this table will remain operational but unsupported, unless explicitly stated otherwise by X-Formation.
Unsupported versions and legacy platforms
LM-X versions older than v6.x may still function in some environments, but they are considered to be unsupported.
For unsupported versions, X-Formation does not commit to:
- Providing security fixes
- Maintaining compatibility with newer components, platforms, or deployment models
- Providing remediation for defects or security issues affecting unsupported releases
To ensure LM-X is operational and secure, customers using unsupported LM-X versions or legacy platforms should upgrade to a supported LM-X version and a currently supported LM-X platform.
Policy updates
This policy may be updated when a new LM-X major release is published, when supported platforms change, or when security and lifecycle requirements require the LM-X support period to be revised.