This page assumes that you already purchased a license. If it is not the case go to the shop page and purchase a license or contact your reseller.


Our networking licenses are distributed in a very usual way. We provide you with a license server software (LM-X from x-formation), and a license file that contains a number of tokens that can be distributed in your local network. Each time a user launches one of our software product, a token is checked out, each time the software product is closed (or even crash), the token is released. If your license allows X tokens, then X clients will be able to run the software simulteaneously.

Note that this page provides the minimal steps required to setup the license system, both on server side and client side. However, you can find here more detailed information about our licensing system software if you would need it.

1 – Install LM-X end user tools

Download and install the server software and its tools on your server machine using appropriate installer depending if you want to run the license server under windows, linux, or macOS.

For Windows Server: lmx-enduser-tools_win64_x64.msi

For Linux Server: lmx-enduser-tools_linux_x64.tar

For MacOS Server: lmx-enduser-tools_darwin_universal.tar

Check “Install LM-X license server” and using the “Browse…” button, specify the location of our Rizom-Lab vendor library that you can download there:

For Windows Server: liblmxvendor.dll

For Linux Server:

For MacOS Server: liblmxvendor.dylib

2 – Get the ethernet address of the machine that will be used as a license server

You should have a 12 hexadecimal length string that looks like this one: 52H62B1BAH52 TIP: To get the server ethernet address, you may use the tool lmxconfigtool, which is included into the LM-X End-user Tools package and present into the license server installation directory.

3 – Tie your license to the license server machine and download your license file

Go to your account and use the “SET” button of the “HostID” field to set the ethernet MAC address of your license server machine. Then click the download button to get your license file. TIP: If you don’t see any floating license in your account it is because either you don’t have purchased any license yet, or because your reseller did not transfer your license yet to your account, or because you are logged using a wrong account.

4 – Copy the license file (.lic) into the license server machine’s hard disk

Simply copy the license file on your machine server’s hard disk.

NOTE: DO NOT INSTALL THE LICENSE FILE ON THE CLIENT MACHINES. The license file must be installed on the server machine only.
5 – Specify the license file location (.lic) in the lmx server config file LMX-SERV.CFG

In the server configuration file lmx-serv.cfg, which can be found in the directory where you installed the license server, add a line like this one (for windows, for unix os, use forward slashes):

LICENSE_FILE = C:\Place\where\licence file resides\your_license_file.lic

More information on the server config file can be found here

6 – On each client machine
NOTE: DO NOT INSTALL THE LICENSE FILE ON THE CLIENT MACHINES. The license file must be installed on the server machine (see above).
Server Path Config

Download and Install the last RizomUV release that you can find here , then set the environment variable LMX_LICENSE_PATH so that it contains the communication port and the ip of the server, e.g:

export LMX_LICENSE_PATH=6200@

Don’t forget to set that variable for all users of the machine so that all of them can use the software.

Please look at this pages to see how to set up the environment variable.

Silent Install

For a silent install of the Windows setups use:

RizomUV_VSRS.XXXX.X.XX.xxxxxx.xxxx.exe /SILENT

or (no GUI at all):

RizomUV_VSRS.XXXX.X.XX.xxxxxx.xxxx.exe /VERYSILENT

Please follow that link to get more information about the installer command line.

7 – Verify that all involved firewalls have their port 6200 open

Check that port 6200 is open on both direction and both on server and client machines for tcp and udp protocols. Notice: You can change the TCP port to another value than 6200. But the UDP must be the 6200.

8 – Troubleshooting