Q100674: How to set up your Team Login render licenses with a render farm

SUMMARY

With the introduction of Team Login licenses, organisations have been granted more control over their licenses when using their software remotely. Setting up your Team licenses for use on a render farm will require some configuration, this article goes through the steps necessary to configure Teams Login licenses with a render farm.

For steps on how to set up a render farm please refer to the following article: Q100104: How to set up Nuke and Nuke licenses for a render farm

MORE INFORMATION

In order to license your render farm using your Team license, please follow the instructions below:

1. Firstly, launch Nuke in interactive mode (i.e, using Nuke's GUI) and log in to obtain the license tokens and preference file. Instructions on activating Nuke can be found here: Q100660: How to activate your Team Login license

NOTE: If you do not have an interactive Teams license please contact Support via these steps as a manual folder will need to be created for your render licenses to work: Q100064: How to raise a support ticket


2. With Nuke now activated, navigate to the directory where these tokens and preference files are stored.

By default this folder can be found in the following directories:

Linux: $HOME/.local/share/Foundry/Tokens

Windows: C:\Users\<USERNAME>\AppData\Local\Foundry\Tokens

OSX: /Users/<USERNAME>/Library/Application Support/Foundry/Tokens


3. Copy the Foundry folder (containing the Tokens folder) to a centrally accessible location such as a network drive. Your set-up on your accessible location should look something like this:

CustomFolder\Foundry\Tokens\token & preference files

 

4. Now your Team license tokens have been set up, you will need to set the following environment variable on both the main machine and the render machines:

“FOUNDRY_CLOUDLIC_READ_DIRS=/path/to/tokens”

This will point Nuke and the render machines to this new shared license token location.

 

Information on setting environment variables can be found here: Q100015: How To Set Environment Variables

NOTE: This environment variable sets the parent directory, so it should point to the folder that contains your Foundry\Tokens\token & preference files. For example, in the following setup, the Foundry\Tokens folders have been placed in a folder named FarmTokens on a shared C: drive:

envvarpath.png

In this case, the environment variable would look like this:

“FOUNDRY_CLOUDLIC_READ_DIRS=C:\FarmTokens”

 

5. With this environment variable now set, your remote render machines should now successfully be licensed using Team Login licensing.

 

FURTHER READING

More information on configuring your Nuke Frame Server or licenses is available in the following articles:

Q100459: Ports used by the Nuke Frame Server

Q100080: Troubleshooting Frame Server issues on external machines

Q100660: How to activate your Team Login license

Q100104: How to set up Nuke and Nuke licenses for a render farm

 

For further information on configuring render farms and Frame Servers, please refer to the following learn page:

Rendering Using the Frame Server

    We're sorry to hear that

    Please tell us why