Q100049: How to avoid using Collective license before non-Collective
A machine using a Production Collective license may run any or all of the products in the Collective simultaneously, and any number of instances of each - limited only by the resources of the machine.
The purpose of having x number of Production Collective licenses is to provide Nuke Studio, Mari, and Modo to x number of machines, so they can be productive with whichever product suits the moment. Therefore, if you have 4 Production Collective licenses, then you can run Nuke Studio, Mari, and Modo on 4 machines.
A machine using a Creation Collective license may run any or all of the products in the Collective simultaneously, and any number of instances of each - limited only by the resources of the machine.
The purpose of having x number of Creation Collective licenses is to provide Modo, Mari, and HieroPlayer to x number of machines, so they can be productive with whichever product suits the moment. Therefore, if you have 4 Creation Collective licenses, then you can run Modo, Mari, and HieroPlayer on 4 machines.
The license manager allocates licenses in the order in which they are found in the license file. The Production Collective or Creation Collective license should probably be made the last one in your server's license file. That way, if one of the other non-Collective licenses is available and can meet the client's need, then it will be allocated ahead of the Collective.
Please note that Nuke requires a nuke_i license, NukeX requires a nukex_i license in addition to the Nuke license and Nuke Studio will require the nukestudio_i license in addition to the previous two licenses, as such if one of these licenses are missing and your Nuke license is above the Collective then the extra required licenses will be taken from the Collective itself, to avoid this you can move the Nuke license after the Collective license in your license file.
You can edit the license file, just use plain text and save it with the same filename. An FLU Diagnostic will show you where it is and what it looks like.
Stop and Start the RLM Server using the FLU to read the updated file.
You also have other ways to allocate: by adding lines to the options file that define users or groups of users and include, exclude, or reserve specific licenses for those users or groups.
Options file syntax is explained in RLM documentation included in your server's Foundry License Tools (FLT) install:
There's an options file in the server's FLT install already. It only has a TIMEOUTALL line in it by default. Diagnostic also shows that file.
We're sorry to hear thatPlease tell us why