What are the current thoughts toward adopting a more modern network license manager, particularly for enterprise customers?
It would be ideal to keep a single network license file on a server and then override that file when there are changes to our license (in my case we are managing hundreds of licenses globally), rather than the current method of managing a list of limited seat license serials attached to a particular disc jacket.
This seems like a business question, rather than a technical question?
Am I confused?
Ha, yes, I suppose you’re right.
The question is: Is the method of network licensing being rethought as part of Rhino 6 development?
No. We don’t have a plan to change our license. But, we will try to make it much easier to manage a large number of licenses.
Basically there are some minor changes to the Zoo that make it possible to have a single license key for a quantity of licenses. Currently we are only using that feature for our school lab licenses.
That sounds great - a single license key would greatly simplify things - thanks Bob.