cart button

Licensing FAQ


Can I transfer my license to another machine?

If you need to transfer a license to another machine, please first read our license transfer policy and complete our license transfer request form.

Please note that you cannot transfer any of our products to a different host system - so for example, you cannot transfer KEYLIGHT on NUKE to KEYLIGHT on Final Cut Pro.


How do I install license keys?

Once you have your license key, please download and use the Foundry License Utility (FLU) to install it on the relevant machine. The FLU will check that the license is valid and then write the license file to the correct locations on your machine, so that the software can find the license. The FLU will install both FLEXlm and RLM licenses.

Installing the license (Mac and Windows)

Download and run the Foundry License Utility (FLU) and select the license install tab. Then 'copy and paste' the license key into the installer window to install your license to the correct directory.

Installing the license (Linux)

Download the Foundry License Utility (FLU) and open a terminal prompt. Navigate to the directory where you saved the FLU and license file and run the following command:
./FoundryLicenseUtility -l foundry.lic

Please note: You may need to run the FLU as Administrator or as a Root user in order to install the licenses.

Installing floating licenses 

If you are installing a floating license, you will also need to set up the license server before it can be used.

Licensing for virtual machines

The Foundry Licensing Tools’ default settings do not support RLM licensing on virtual machines (VMs). If you have any questions regarding licensing on VMs, please contact support@thefoundry.co.uk for more information. Please note that you cannot serve floating licenses for MARI, HIERO, KATANA and OCULA from a virtual machine.


What is the system ID and how do I find it?

A machine's system ID is a unique code required to license products from The Foundry. Please note that refunds cannot be given for licenses issued for an incorrect system ID, so please download a tool (below) to report the correct system ID.

System ID for trial or node-locked licenses

For trial and node-locked licenses, you need to find the System ID of the machine that will use the software.

System ID for floating and render licenses

Floating licenses are managed by a machine on your network acting as a license server. When buying a floating license, you need to enter the System ID of this license server. 

Finding the System ID

  • Download the Foundry License Utility (FLU) to find your system ID:
  • Mac and Windows users: Run the FLU. The System ID will be displayed at the bottom of the window.
  • Linux users: run the following command in the directory where you downloaded the FLU to print out the System ID:
./FoundryLicenseUtility –i
  • If the System ID is of the form Raaaaaaaaaaaa:Xbbbbbbbbbbbb, please see What do I do if the FLU returns two system IDs?

Where can I find the Foundry’s licensing utilities?

We've consolidated all our licensing utilities into two downloads:

Foundry License Utility (FLU)

Foundry License Tools (FLT)

These tools work with both FLEXlm and RLM licenses from The Foundry.

These tools replace the following deprecated tools: Foundry System ID (FSID), Foundry License Installer (FLI), Foundry License Diagnostics (FLD), Foundry FLEXlm Tools (FFT) and Foundry Licensing Tools (FLT) version 6.0 and earlier.


What is the Foundry License Utility (FLU)?

You can use this utility to find a machine's system ID, install license keys or diagnose license issues. The FLU works with both FLEXlm and RLM licenses from The Foundry.

The FLU replaces the following deprecated tools: Foundry System ID (FSID), Foundry License Installer (FLI) and Foundry License Diagnostics (FLD). 

Download the Foundry License Utility (FLU) 7.0v5

Please note that if you have already installed the Foundry License Tools (FLT) 7.0 on your license server, the FLU will also have been installed on that machine. This will not have been installed with older versions of the FLT.


What are the Foundry License Tools (FLT)?

This utility contains both FLEXlm and RLM license servers, a copy of the Foundry License Utility (FLU) and relevant license documentation. Once the Foundry License Tools (FLT) are installed, the FLU will display additional tabs to allow you to manage your FLEXlm and RLM servers.

Download the Foundry License Tools (FLT) 7.0v4

 


What are RLM and FLEXIm licenses?

We currently use two different licensing solutions to license our software, FLEXlm and RLM. Which licensing technology is used depends upon the product.

Prior to the release of Foundry License Tools (FLT) 7.0, we had two separate sets of license tools depending upon which kind of licensing was required - Foundry FLEXlm Tools 5.0 for FLEXlm and Foundry Licensing Tools 6.0 for RLM. This meant that customers using different software from The Foundry might have required multiple downloads to license their products.

The latest version of our Licensing Tools, FLT 7.0 consolidates both the FLEXlm and RLM server software into a single download. Installing FLT 7.0 requires the removal of old versions of the Foundry FLEXlm Tools and Foundry Licensing Tools 6.0.

The new Foundry License Utility (FLU) has all the functionality of the old Foundry System ID tool (FSID), the Foundry license Installer (FLI) and the Foundry license Diagnostic (FLD) tools for both FLEXlm and RLM and can be used to administer both FLEXlm and RLM floating licenses.

Production COLLECTIVE and the Creation COLLECTIVE are licensed using RLM licensing.

When not purchased as part of a COLLECTIVE, MARI, HIERO, KATANA and OCULA are licensed using RLM licensing.

When not purchased as part of a COLLECTIVE, NUKENUKEX, FURNACE, CAMERATRACKER, KEYLIGHT and KRONOS are licensed using FLEXlm licensing.


What do I do if the FLU returns two system IDs?

For most machines the RLM System ID and FLEXlm System ID are the same, so the FLU will display a single System ID. However, on rare occasions, you can have two System IDs reported (one for RLM and one for FLEXlm). If this is the case, both System IDs are displayed, like this:

Raaaaaaaaaaaa:Xbbbbbbbbbbbb.

If the FLU returns two System IDs for your machine, the one that you need to use depends on which software you are running:

  • For RLM licensed software you need to use the first System ID minus the R, e.g. aaaaaaaaaaaa in the above example.
  • For FLEXlm licensed software you need to use the second System ID minus the X, e.g. bbbbbbbbbbbb in the above example.

How do I remove the Foundry licensing tools?

Removing FLT version 7.0

To un-install FLT 7.0, please run the uninstaller script that is installed in the LicensingTools7.0 directory.

Removing FLT version 6.0

To un-install FLT 6.0, please run the uninstaller script that is installed in the LicensingTools6.0 directory.

Removing FFT version 5.0

To un-install FFT 5.0, please run the FFT Uninstaller that is installed in the FLEXlmTools5.0 directory.

Removing FFT version 4.0

If you need to remove FFT 4.0, please follow the instructions below:

How to Remove FFT 4.0 from Mac OS X

  1. Open a terminal from /APPLICATIONS/UTILITIES
  2. Login as root
  3. Type /usr/local/foundry/FLEXlm/lmutil lmdown -c /usr/local/foundry/FLEXlm/foundry.lic [ENTER]
  4. Remove the old server by typing:
rm -r /Library/StartupItems/FoundryFLEXlmServer [ENTER]
rm /usr/local/foundry/FLEXlm/lmgrd [ENTER]

How to Remove FFT 4.0 from Windows

  1. In the start menu search box, type cmd [ENTER] to bring up a console
  2. In the console type C:\Program Files\The Foundry\FLEXlm\remove.bat [ENTER]

How to Remove FFT 4.0 from RedHat/Centos Linux

  1. Open a terminal
  2. Type /etc/init.d/foundrylmgrd stop [ENTER]

How to Remove FFT 4.0 from Debian Linux

  1. Open a terminal
  2. Type /usr/sbin/update-rc.d -f foundrylmgrd remove [ENTER] 

How to Remove FFT 4.0 from SuSE Linux

  1. Open a terminal
  2. Type /sbin/chkconfig --del foundrylmgrd [ENTER]

What do I need to do if I’m using a floating license?

In order to use a floating license for products, you need to install Foundry License Tools (FLT) on your license server. Do not install these on client machines.

The FLT contains both FLEXlm and RLM license servers so they can be used to manage floating licenses for all The Foundry software.

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.


Are there any known issues with OS X Mountain Lion?

There is an issue with OSX Mountain Lion and some of our products that causes the valid FLEXlm SystemID for a machine to switch back and forth between MAC addresses for the machine, resulting in valid licenses being reported as invalid. This problem can affect NUKE and NUKEX, FURNACE, FURNACECORE, CAMERATRACKER, KEYLIGHT, KRONOS and ROLLINGSHUTTER.

If you encounter this problem, please generate the diagnostic output from the Foundry License Utility (FLU) from the machine affected and send it to support@thefoundry.co.uk. We will be able to reissue a license to enable you to avoid the problem once we verify that OS X Mountain Lion is the cause.

To find out how to generate diagnostic output, see "How do I report diagnostics to the Foundry?"


Are there any known issues with Windows 7?

Sometimes our software may give you licensing errors on Windows 7, even when the Foundry License Installer (FLI) reports that the license was installed successfully.

This problem appears to happen on Windows 7 because of the extra ProgramData directory - Windows 7 has the same Program Files and Program Files (x86) folders as Windows XP, but it also has the new ProgramData folder.

On XP, both NUKE and plug-ins look in C:\Program Files\TheFoundry\FLEXlm for a license.

On Windows 7, The FLI presently installs licenses to C:\ProgramData\The Foundry\FLEXlm only. NUKE will look in this directory for a license as well as the old one but plug-ins such as OCULA for NUKE or CAMERATRACKER for After Effects, and NUKEX features (which are effectively plug-ins) only look in the old C:\Program Files\The Foundry\FLEXlm location. Therefore, if you only have license files in C:\ProgramData\The Foundry\FLEXlm, plug-ins and NUKEX features will not be able to find your license.

You can solve this problem by copying your license file(s) (these will have a .lic extension) from

C:\ProgramData\The Foundry\FLEXlm

to

C:\Program Files\The Foundry\FLEXlm

Please note that in order to see the ProgramData directory in Windows Explorer, you have to turn on "Show Hidden Files and Folders" in the Windows Folders and Properties - View options.

Please note that if you are using 32-bit plug-ins, then you will also need to copy the .lic file to

C:\Program Files (x86)\The Foundry\FLEXlm


How do I report diagnostics to the Foundry?

If you are encountering problems with your licensing, please download the Foundry License Utility (FLU), run it on the affected machine(s) and then follow the instructions below to report the diagnostics to us.

Reporting diagnostics: Mac and Windows users

  1. In the Diagnostics tab of the FLU interface, click Run Diagnostics and save the output file.
  2. Send the file to support@thefoundry.co.uk along with a description of the problems you are encountering.

Reporting diagnostics: Linux users

  1. Open a terminal prompt, navigate to the directory where you saved the FLU and run the following command:


    ./FoundryLicenseUtility -d

  2. Save the file and send it to support@thefoundry.co.uk along with a description of the problems you are encountering.