We have 3 of our four rhino 8 licenses in use by named users - but our fourth license is unusable as it says for one seat “seats in use by related products.”
What is causing this? It’s impossible to attribute to whom this forth license is mysteriously attributed to as you can see only 3 users are listed. On our end, it seems none of these users are using additional software/plugins such as rhino.inside, etc… - just regular rhino 8.
Some help would be appreciated considering we effectively have 3 licenses available despite purchasing 4.
This is caused by shared licenses between Rhino 8 and 7. When you upgrade from a Rhino 7 license to a rhino 8, that license has the ability to open both software versions.
You may notice that if you add your rhino 7 and 8 licenses from the “live usage” page adds up to MORE than the total licenses you own.
When someone opens up a Rhino 7, it grabs the first license available, which COULD be one of the upgraded rhino 8 licenses. This can also happen vice versa. When this happens, that license will NOT show up in the live usage for the other version.
This is a problem that Mcneel should fix so that all licenses in use show up in the live usage, but rest assured, you ARE using all of the licences you paid for.
@Ian19
On the Support page, use the “Find your license key” tool and you will see your rather complicated set of licenses and how they are linked.
You have a total of 10 licenses in your team.
5 are V7 only
2 are V8 only
1 is a V5, V7, V8 chain
1 is a V5, V6, V7, V8 chain
1 is a V6, V7 chain
Only V6 and newer licenses can be in your license Team.
A couple of points here that are not super obvious:
Per McNeel’s EULA, a license upgrade allows you to run a newer version of Rhino, but does not increase the number of seats available. So, if you have a Rhino 6,7,8 upgrade cluster, you can use it to run 6,7, or 8, but only one seat at a time.
Given #1, Cloud Zoo is “customer-friendly” in the sense that it will do graduate-school level combinatorial math to figure out if there’s any possible combination that would let users with clustered license chains run Rhino. Since Cloud Zoo never actually hands out licenses to Rhino, this is recomputed on-the-fly every time a Rhino client (V6 or later) requests a license lease.
In spite of all the wonderfully clever magic of administering all of a user’s licenses, it seems to this innocent standalone licensed single user bystander that the “live usage” page is the convenient goto page for quick user situational awareness and should show ALL the usage at a glance even in these complicated licensing situations.
