Understanding Cloud Zoo Team Licensing administration

Rhino Rhino for Windows
1

Hi there, wanted to clarify the behaviour of how cloud zoo licensing works. Was not able to find clear answers on the below searching online, and we have been running into issues managing our teams licenses recently;

  • Is there a way to remove or “kick out” a user from the admin side?

  • What is supposed to determine when a license is supposed to be released? I suspect at least a few of our licenses are “stuck” but would like to verify what the intended behaviour is here first.

  • Is there a recommended “best practice” for users to ensure their license is properly freed when they are no longer working in Rhino?

  • Are there intended circumstances where a user can be kicked out of the program while actively working, due to full licenses?

Many thanks for any help clarifying these points.

2

Hi Admin,

In general the license return should be almost instantaneous, with a clear internet connection.

  • Is there a way to remove or “kick out” a user from the admin side?

https://accounts.rhino3d.com/help#group_admin_tasks

  • What is supposed to determine when a license is supposed to be released? I suspect at least a few of our licenses are “stuck” but would like to verify what the intended behaviour is here first.

When the user has closed the program.

  • Is there a recommended “best practice” for users to ensure their license is properly freed when they are no longer working in Rhino?

with no Rhino instance active (checking task manager), there have been cases where plugins have interrupted this

  • Are there intended circumstances where a user can be kicked out of the program while actively working, due to full licenses?

no that i’m aware of

3

As the Team Owner/Admin, I would recommend you setup Remote Desktop or equivalent on remote computers so you can go in and look for Rhino left running.

4

Thanks for the responses, I will have to dig further then as we have definitely had cases where the above did not occur as expected.

@John_Brock We, of course, have this capability. As I’m sure you can appreciate, past a certain volume of users individually policing each user is not a good solution.

5

Agreed.
My guess is if you check the systems that have not released a license, you will find a Zombie Rhino running in Task Manager, most likely caused by a third-party plug-in not closing properly and leaving Rhino “headless”.

6

worthy of note, but might not be applicable to your situation is that Rhino.Inside (Revit, Tekla,…) will not show up on the Task Manager since its running inside the other process.

I would need to close Revit completely to release this license.

image
image1030×571 54.3 KB