Create a ticket

Q100027: How to install a floating license


This article illustrates how you can install and use floating RLM and FLEXlm licences from the Foundry.  This covers both how to install and run the licences on the server machine and how to connect the other machines on your network to the license server so they can use the licenses.  Note that these other machines are referred to as "client machines" in licensing terminology.


On the server side, you will need to install the Foundry License Tools (FLT) on your server machine and install the license keys using the Foundry License Utility (FLU). On the client side, you can install the license using the FLU or the Product License Dialog.

This article is relevant for Nuke, Mari, Hiero, Ocula, Collectives and RLM Modo licenses as part of a Collective.


NOTE: Instructions on how to activate login-based licenses for Modo 11 (Modo Subscription or Modo with Maintenance) can be found in Q100283: How to activate a Login-based or Subscription License

NOTE: If you purchased Modo 10 series or earlier on its own then please see Q100139: How to Install a Legacy MODO License



In order to use a floating RLM or FLEXlm license for our products, you need to install the Foundry License Tools (FLT) on your license server machine to manage the licences and make them available on your network.  
NOTE: The FLT installer will warn you to not install the tools on a client side machine.
The licensing tools are required for a floating license to work, so if you are going to run the program you have a floating license for on the machine that is also floating the licenses then please ignore this warning.
The FLT install also includes the Foundry License Utility (FLU) which is used for installing licences, starting/stopping the servers and diagnosing licensing problems.
After installing the license server tools, the next step is to install the floating license(s) on the server.

OSX and Windows 

  1. Download and install the Foundry License Tools (FLT)
  2. Run the FoundryLicenseUtility as an admin user.
    - On OSX this will be installed to Applications > The Foundry > Licensing Tools 7.1.
    - On Windows, from the Start menu, navigate to All Programs > The Foundry > FLT 7.1v1 then right click on the "Foundry License Utility" and select "Run As Administrator".

  3. Either drag and drop the license file or copy and paste the full license key text in to the 'License Install' tab of the FLU.  The FLU should report that the license was successfully installed and list the location(s) where it is saved.

  4. The FLU will ask if you wish to start or restart the RLM/FLEXlm server.  Please click Yes.

  1. Download the Foundry License Tools (FLT) 

  2. Unzip the download and run the script in unzippped FLT directory, this will install the tools on the machine.

  3. Open a terminal and run the following commands as a Root user or with sudo to install the license file on disk:

    cd /usr/local/foundry/LicensingTools7.1/
    ./FoundryLicenseUtility -l /path/to/foundry.lic

    (Where /path/to/foundry.lic is the full path to where you've downloaded your floating licence file)

  4. The FLU will ask if you wish to start or restart the RLM/FLEXlm server.  Please enter Yes and hit return.
NOTE: Please do not install FLT on the client machines, they are only needed on the license server.
You can point your client machines toward the license server using either the product's license dialog, the Foundry License Utility or by setting an environment variable.
Using the Product License Dialog
If the product has a license dialog then this can also be used to install a license by doing the following:

1. Download the product installer for your platform and install it.

2. Launch the product.

NOTE: On Windows please launch the product as administrator by using the right click context menu option 'Run as administrator' to install your license to the correct directory.

3. The licensing dialog will appear when the program fails to find a license. Select 'Install License' then select 'Use Server'.
4. Type <number>@<server name> (for example, 4101@red) and click Install. For Nuke select RLM server as the Server Type and Click OK.
This will install a client license file on disk enabling the machine to get a license from the server.

5. Click Launch to launch the product
Using The Foundry License Utility (FLU)

The Foundry License Utility (FLU) will verify a license for you and install it to the correct location(s) on your machine.

OSX and Windows

1. Download the Foundry License Utility (FLU)

2. Run the FLU as Administrator or as a Root user.

NOTE: On Windows you can run the FLU as administrator by using the right click context menu option 'Run as administrator'. 

3. Run the FLU on the client machine and paste the following line into the License Install tab:

HOST <server name> any 4101

replacing <server name> with the hostname of your server, e.g.

HOST red any 4101


1. Download and unzip the Foundry License Utility (FLU)
2. Open a terminal and browser to the directory location where you unzipped the FLU download.
3. Run the following command as a Root user:

./FoundryLicenseUtility -c 4101@<server_name>

replacing <server_name> with the hostname of your licence server, e.g.

  ./FoundryLicenseUtility -c 4101@red

The FLU will create both an RLM and FLEXlm client licence

This will install a client licence file on disk enabling the machine to get a licence from the server.

Using an environment variable

As an alternative to creating a client license file you can set an environment variable called "foundry_LICENSE" to point toward the server.  For example, if your licenses are running on port 4101 on a server machine called "red" then you would set



For help with setting environment variables please see Q100015: How To Set Environment Variables

More information

Please refer to the Foundry Licensing Tools User Guide for instructions on how to run the Foundry license tools and float licenses on your network.





Keywords: floating, license, installation, FLT, FLU

Was this article helpful?

We're sorry to hear that!

Please tell us why.
8 out of 30 found this helpful