SUMMARY
License roaming happens when a Floating or Team Login license is checked out for a number of days so you can keep running the software when off the network or offline.
These instructions are relevant for Team Login licenses from Nuke 14, Mari 7 and Modo 17 and above, and for Floating RLM licenses for Modo 15, Nuke 13.2 and Mari 4 and above. If you are roaming an earlier build of the software with a Floating RLM license, please see: Q100583: How to roam a Modo/Nuke license from a server from an older build
NOTE: Roaming a license is only possible for standalone RLM or Team Login licenses. It isn't possible to roam a license from a Collective license.
NOTE: After two decades of 3D workflow innovation, we have made the difficult decision to discontinue Modo, following the release of 17.1. More information on this can be found here
MORE INFORMATION
License Roaming is available with the following license types
- Floating RLM Licenses for Nuke and Modo
- Team Login Licenses for Nuke, Modo and Mari
If roaming is not enabled for you and you would like to roam licenses, then please open a support ticket to request this following the guidance here: Q100064: How to raise a support ticket
ROAMING TEAM LOGIN LICENSES
NOTE: If you are using Nuke versions released prior to May 20th 2025, and you encounter failed checkout errors when attempting to launch Nuke with a Teams Login License, please refer to the following article: Q100721: Advisory on resolution of Teams Login-Based licensing system errors
You can roam a Team Login license within your Organization by launching the software you wish to roam a license for, and from the menu clicking on the following option:
Nuke: "Help > License..."
Modo: "Help > Modo Licensing..."
Mari: "Help > License"
A Licensing UI dialog will appear and from there, you can select "Manage Team Login Roaming" as seen below:
Next select the "Roam login license(s)" button to roam your Team Login license for 30 days.
You will only be able to roam a Team Login license for 30 days. There are no options for roam for more or less days. However, this duration will be extended if you connect to the internet while the license has been roamed.
RETURNING ROAMED TEAM LOGIN LICENSES
After the 30 day period, if you have not connected to the internet during that time, the roamed Team Login license will be automatically returned to the organization. If you have connected to the internet during the roam period then your roam period will have been extended.
If you no longer need to roam your license from your organization, the license can be returned from the machine that has roamed the license.
NOTE: It is not possible to reclaim the license using the Teams Organization Dashboard.
To return the roamed Team Login license, please do the following:
- Reconnect the device with a roamed license to the internet.
- Launch Modo/Nuke/Mari and navigate to "Help > Modo Licensing..." or "Help > License...", then click on "Manage Team Login Roaming"
- Hit "Return Roamed Login Licenses" then exit the application.
These steps will return your roamed license to the organization.
ROAMING A FLOATING RLM LICENSE
You can roam a Floating RLM license by launching the software you wish to roam a license for, and from the menu clicking on the following option:
Nuke: "Help > License..."
Modo: "Help > Modo Licensing..."
Mari: "Help > License"
A Licensing UI dialog will appear and from there, you can select "Manage RLM Roaming" as seen below:
Enter the number of days you want to roam your license while offline and click on "Roam licenses"
You can then take the machine offline and use the license for the specified number of days, after which it will be automatically checked back in to the RLM server.
RETURNING ROAMED FLOATING RLM LICENSES TO THE LICENSE SERVER
By default, your machine will keep the license checked out for the full roaming period set. Once the roam has timed out, the license will be available again on the license server and the machine cannot run the software until it reconnects to the license server.
If you want to return a roamed license, you need to do this from the machine that checked the license out.
NOTE: It isn't possible to reclaim it from the RLM license server.
To return the roamed Team Login-Based license, please do the following:
- Reconnect to the same network as your license server.
- Launch Modo/Nuke/Mari and navigate to "Help > Modo Licensing..." or "Help > License..." and then click on "Manage roaming"
- Hit "Return Licenses" then exit the application and the license will be returned to the server.
NOTE: The "Return Licenses" button only appears if you have already roamed a license and then restarted the software, it doesn't appear in the same session that you roamed the license from.
HOW TO CONTROL ROAMING BEHAVIOUR WITH RLM FLOATING LICENSES
By default, all RLM Floating roaming enabled licenses could be roamed from the server by any user or machine on the network running a compatible application.
You can control access to license roaming on your server by adding the commands below in the "foundry.opt" options file. Information in how to use and edit the options file is in Q100107: How to reserve licenses for different users or machines.
- You can limit how long licenses can be roamed for with "ROAM_MAX_DAYS num product". For example, to limit roaming of Modo licenses to 20 days you would add
ROAM_MAX_DAYS 20 modo_i
- You can limit the number of licenses that can be roamed with "ROAM_MAX_COUNT num product". For example, if you have 20 NukeX licenses but want to allow up to 5 of them to be roamed at any one time you would add
ROAM_MAX_COUNT 5 nuke_iROAM_MAX_COUNT 5 nukex_i
- You can restrict license roaming to only specified users or machines with "INCLUDEALL_ROAM user|host|group|host_group|internet|internet_group|project who". If you wanted to only make license roaming available for a group of 4 users you need to create a group and then add the command to just include them like the following
GROUP bugs john paul george richardINCLUDEALL_ROAM group bugs
- You can prevent named users or machines from being able to roam licenses with "EXCLUDEALL_ROAM user|host|group|host_group|internet|internet_group|project who". If you wanted to prevent a set of machines from being able to roam licenses you first create a HOST_GROUP and then add the EXCLUDEALL_ROAM line like the following
HOST_GROUP temp_workstations temp_vfx01 temp_vfx02 temp_vfx03 temp_vfx04EXCLUDEALL_ROAM host_group temp_workstations
FURTHER HELP
If you are still experiencing difficulties please create a support ticket to let us know the exact issue encountered and the troubleshooting steps that have been taken.
For more information on how to open a support request, please refer to this article: Q100064: How to raise a support ticket
FURTHER READING
More information on licensing roaming can be found in the links below:
Q100583: How to roam a Modo/Nuke license from a server from an older build
We're sorry to hear that
Please tell us why