It’s not clear how floating license management is designed to work with student computing labs in educational environments. From the documentation it looks like it follows the Rhino Cloud Zoo model, where access to a cloud-based license pool (“key”) is available after completing an emailed invitation/acceptance process. For smaller groups, e.g. a single class or two, this is manageable but if the lab is a resource for a large student population (500+) this can be a challenge to manage – comprehensive user lists need to be prepared, clear communication on the process needs to be provided, a continuing period of maintenance needs to be included for those who lost the message (many students ignore email they don’t recognize), and another period of user management at the end when students enroll/graduate. The licensing approach Chaos Group has been using for V-Ray is more straightforward – straight concurrency. We were hoping to avoid node-locked licensing, which we have been using up to this point, because of the per machine installation/removal process as machines are reloaded. For those who have deployed floating licenses, is this how it works, and for educational environments, which have you chosen?