Q100361: How to update to Foundry Licensing Tools 7.3v1
A new version of the Foundry Licensing Tools (FLT) has been released. This article explains how to update to the latest version of the tools and why we would recommend that users do this.
With the release of the FLT 7.3v1 we have updated the internal license server code to RLM version 12.2. The previous public release, FLT 7.1v1, used RLM 9.4.
We are in the process of updating our products to use newer versions of RLM too - Nuke 11.0 was the first release to use RLM 12 in its internal licensing code and this has been followed by Mari 4.0. To avoid any problems using floating licenses with Nuke 11.0, Nuke 11.1 and/or Mari 4.0 we would recommend updating your licensing tools to FLT 7.3v1.
Major new versions of other products will also be updated to use RLM 12 in the future so we recommend that all customers with floating licenses update to FLT 7.3v1 when possible.
You can update to
- Uninstall FLT 7.1v1 by following the instructions in Q100133: How to Uninstall the Foundry Licensing Tools
- Download FLT 7.3v1 from the licensing page of our website
- Install FLT 7.3v1 on the server by following the instructions in Q100360: How to install the Foundry Licensing Tools (FLT)
The RLM server should then start up and your licenses will be available.
If you encounter any problems with your licenses when updating the Foundry Licensing Tools then please follow the instructions in Q100105: Diagnosing License Problems to generate a diagnostic file from the Foundry License Utility and open a support ticket.
Detailed information about the Foundry Licensing Tools can be found in the Foundry Licensing Tools User Guide.
For more information about getting up and running with your licenses, please see the following articles on the Support Portal:
- Q100002: What is the System ID and how do I find it?
- Q100026: How to install a nodelocked license
- Q100027: How to install a floating license
- Q100264: How to point a machine to your RLM license server
- Q100105: Diagnosing License Problems
We're sorry to hear that!Please tell us why.