Cloud Zoo License Management Available in Rhino 6

I only see one possible problem here and that would be with the machine connected to the laser.

If you are always careful to close Rhino on one machine before running it on the other, then the situation with V6 is that you will have to occasionally have to have both of the machines connect to the internet - about once every two weeks. I assume the one that you “conduct daily business” with will not have a problem with that as you probably run e-mail, web, etc. on that one.

If the machine that runs the laser has to be absolutely isolated from the internet, then that’s an issue that will be difficult to solve without buying a separate license for it. If it can connect occasionally, there isn’t really a problem…

I’m curious to know what “reasonable proof” that “many” users were abusing the terms of use would be?

Assuming your assessment is reasonable, is this a situation where McNeel perceived the ratio of abusers to honest users of multiple machines became too high to be ignored? Another situation where the few bad apples ruin it for the rest of us? Certainly McNeel isn’t so naive as to think there would not be any dishonest users; I always assumed they just wrote them off to marketing promotion and goodwill.

I have also always felt that a large portion of Rhino users, perhaps a majority, were people like Lauren and myself: individuals with more than one computer with Rhino installed for whom it is physically impossible to operate multiple installations simultaneously. The one situation where simultaneous use of Rhino might occur would be when one installation was doing a rendering while active modeling was being done on another. This was previously interpreted as being no different than running two instances on one machine for the same purposes and thus permitted under the terms of use.

In my case all my modeling is done on offline machines (mainly one). Apparently if I want to own two offline machines with Rhino installed I will now need two Rhino licenses, effectively doubling my Rhino cost for no change in the operating convenience I have enjoyed for several decades.

One of the things that has historically contributed to my respect for McNeel as a company was the trust and respect for users implied by the terms of use and many other aspects of their customer relations. It saddens me that they feel they can no longer serve their offline users without forcing them to double their licensing cost or connect their machines to the internet.

Hopefully your ongoing consideration of these policy changes can come up with something better for users like me.

For those with a desktop and laptop at their sole disposal, whom go on the road periodically, and whom have never had to wrestle with the new ‘two week auto’ construct in past, I was wondering if a more overt checkout option might help, if technically feasible? Perhaps in addition to the existing ‘two week auto’ construct.

I’m referring to existing floating license solutions; where we may manually ‘checkout’ a license, and define the term, and then manually ‘return’ the license early, or allow it to automatically return at the end of the manually defined period.

At least such an option would give the road warrior a premeditated means to insure that he/she is not ‘somewhere’ stuck in an “aw @#$&” moment, scrambling to rectify.

Just a thought. (Which I suspect may have been vetted previously?)

1 Like

That has never been permitted under the EULA as far as my recollection is concerned… correct me if I’m wrong. One license of Rhino is not supposed to be running on two machines at the same time, no matter what the circumstances.

I could be the one who is wrong. My recollection goes back to the days when rendering took a really long time and was usually done on a separate machine or group of machines. I recall much discussion on this point and thought it was resolved in favor of not requiring a user to have a second Rhino license to accomplish rendering on a second machine which could otherwise be done with a (permitted) second instance on the primary machine.

Hi, Any way to either reset/logout manually whatever - the cloud zoo should be transparent and working…but it does not…I have just upgraded and tried the zoo on my 2 computers - first on the laptop and then on the desktop - which fails - Rhino6 was not working on the laptop at the time I was trying on the desktop…I even got an e-mail regarding the login trial…(I prefer the hardware key I have with Archicad if it is supposed working like this)
Sorry but the first impression of the new licensing system is no good ;(

Error messages? screenshots?

I answered by e-mai(so it might be duplicated)l: Now it works - conclusion might be: that the restart of the machine after installing might have helped…wired because on the laptop it was not necessary.


There is a bug in Windows affecting some machines that disables programs from being able to open links in a browser. The workaround is to reset Window’s default web browser, then try again. I have re-written the login code in 6.4 so that Rhino does not depend on Windows to login.


It might be something else - the link was opened…the login and pass was put and accepted.
so after restart I did not have to log in again…and it worked (as I have written in the e-mail)

Are there any really clear to follow instructions out there that describe the process I should follow to upgrade a license from our current local zoo to the cloud zoo? Everything I’ve found is too simplistic.

I have purchased the Rhino 6 upgrade and have the new license code. And I have added this to the team in the cloud zoo but it then asks for the license key from the previous version. I’ve tried entering this but get the error “The license key you are upgrading from is not valid or has been disabled”.

Any idea what that means and how I can sort it? Do I have to remove the old R5 license from the local zoo first? If so how does 1 do that? All I can see is delete license, which is kind of scary.

Contact your regional Sales office to figure out what the issue is with your V5 license key.


A couple of questions after reading through this and they may have been answered, they may not have, forgive me either way:

Within a corporation, does each user need to have a Rhino account in order to use the Cloud Zoo? (Corp is of about 10 users). If so, does each user need to login to that account, upon each time they want to use Rhino?

How do I stop ex-employees (terminated, departed etc.) from using those seats?

We still have two Rhino 5 licenses in the Zoo which I’m fairly certain I will upgrade soon/immediately - are there any issues with v5 licenses in the Cloud Zoo?

Thanks in advance.

You can create a “Team” for you V6 licenses and then link a Domain so anyone with a Domain login, will have access to the team licenses. Then the individuals do not need Rhino accounts.

Take a look at these details:

V5 licenses are not supported by the Cloud Zoo; only V6 and V6 plug-in licenses.

If so, does each user need to login to that account, upon each time they want to use Rhino?

No, only the first time they use Rhino on their computer. If it is a shared computer, then logging out after a session is recommended.

How do I stop ex-employees (terminated, departed etc.) from using those seats?

You can remove them from your team at any time, which will automatically deny them access to the team’s resources.

Thank you @John_Brock and @aj1 for the responses, I think pooling all our licenses in a team and having users access them that way will be useful. I know that with any logging in as such, will create a bit of frustration.

In terms of the v5 licenses, we still have two that we have converted to v6 yet due to some users still needing plug-ins that are still only associated with v5. Do you recommend that those v5 licences remain on the regular Zoo for now?

Yes. Leave your V5 licenses just as they are now.

We want Rhino 6 to logon with our cloud account without the users getting they’re hands on the credentials.
Is it possible to silently login the account, or add the cloud license without user interference?

Can you be more specific in describing what you are trying to accomplish? Since the whole login scheme is designed to ensure that only authorized individuals are using Rhino on a one-user/one license basis at any given time, your question as stated doesn’t make much sense (at least to me).

If you link your Domain to the Rhino Cloud Zoo team, then their Domain login will let the start Rhino.
Here’s a link to the details about Teams: