If I change the license server setting, should Deadline propagate that out to all the clients? Or will I have to go to each client and make the change?
This is a complex question, as there are so many ways to change licensing.
First of all, the license model is stored in the deadline.ini file which is local to every machine (workstation or render node). So while it is possible to edit that file, it is not very practical.
On a workstation with a non-service Launcher, you can also easily open the Launcher menu, select Change License Server…, and use the dialog. But that is again not optimal for render nodes.
So we get to Auto Configuration. In the Tools (Super User Mode) > Configure Repository Options > Auto-Configuration dialog, you can create a ruleset to enforce a new licensing mode (and a bunch of other things, if you want).
When a Worker connects to the Repository, it checks the Repository for Auto Configuration rulesets and applies them if they are enabled. This will have the effect of writing to the deadline.ini config. file, so once you have enforced these settings, you could even disable the ruleset and the Workers will still keep their last enforced license mode.
Note that this also lets you use an IPv4 filter, which defaults to any machine, but you could affect only a specific subset of machines if necessary. Usually you will just leave it at *.*.*.*
1 Like
Thanks for the robust answer. I actually did set an auto config for this. But it seems like I had two issues. One was that it took a long time for those changes to propagate, like 15-20 min it seems. Two, I was using just @licenseserver instead of 27008@licenseserver. Once I made that change things started falling into place.
Since the Auto Configuration applies on Worker startup, you would have had to use Remote Control to Restart all Workers. Did you force them to restart?
Yeah eventually I did a mass restart.