Automated Installation of Rhino 7 - Cloud Zoo

[jfreund (Joseph Freund)]

Hi all,

I just want some clarification for setting up a deployment / automated install of Rhino 7. I am following the instructions here: Automating installation of Rhino 7 for Windows [McNeel Wiki]

For specifying the Cloud Zoo for LICENSE_METHOD it says to leave blank. Does that mean the argument should be:

LICENSE_METHOD=

or should the parameter be removed from the string of arguments? I have an admin that is getting an error that “Zoo Server is not available” with the following string of arguments:

-package -quiet -norestart LICENSE_METHOD= INSTALL_EN=1 ENABLE_AUTOMATIC_UPDATES=0

Thanks in advance!
JF

[jfreund (Joseph Freund)]

From what I gather, if a valid license is not found via the specified LICENSE_METHOD, the following window will appear:

Is there any way to suppress this for deployments and have it go straight to the window below? Not a big deal, just asking for a friend

Thanks,
JF

[John_Brock]

You don’t need the LICENSE_METHOD arcument at all.
Then when an individual starts it, they will need to Login as you’ve shown so Rhino know who is running it and can check if they have a Personal or Team license.

Then the user can Logout, and the next user can start Rhino and Login.

[jfreund (Joseph Freund)]

Thanks, John. I will advise them to not include the LICENSE_METHOD parameter.

Will the next user have to agree to the EULA too? If not, is there a way for the Administrator to ‘silently’ agree to the EULA on behalf of all of the users when deploying to all computers?

Thanks,
JF

[John_Brock]

The only way I can think of would probably open a bigger can of worms than you want to deal with.

This would be to connect the Domain to the Team.
Then anyone with a Domain login is automatically a Rhino Team member. Then the user doesn’t do anything other than be using a Domain login to get into Windows.
Details:

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

[jfreund (Joseph Freund)]

Thanks, John. I’m no stranger to cans of worms, just trying to reduce the probability of internal support requests for an IT Director friend.

I have more questions about Domain Linked Teams here :

Logic of Which Team to Pull License (Domain Linked, Multiple Teams)

I have a couple questions regarding managing users, licenses, and teams: Scenario 1: Team A - 10 licenses of Rhino 7 - 20 members added to team (all with email @microsolresources.com) Team B - 10 licenses of Rhino 7 - Domain Linked (microsolresources.com) When a member of Team A opens the software for the first time and logs in with their email, will it prioritize pulling the license from Team A, despite having an email with the same domain as the domain linked Team B? Scenario 2: Team A -…

[John_Brock]

I’m going to defer to Andres, the developer of these tools.

Yo @aj1, can you please have a look?

[aj1 (Andrés Jacobo)]

Hi @jfreund, early in the Cloud Zoo’s integration with Rhino we decided that it would be rare for a user to belong to 2 different teams which both have a license.

Rhino will always try to grab a license from your personal account if one is available. If it isn’t, it will go look for a license in a random team and stick to that team unless the lease expires or the team is out of licenses.

This behavior can be customized by going to Tools -> Options -> Advanced and setting Rhino.LicensingSettings.ManualEntitySelection to true (In Mac, Go to Rhino -> Preferences -> Advanced). Then, run the the Logout command. This will close Rhino. When you open Rhino again, Rhino will always ask you where you want to get a license from. This is probably the best solution for you as long as users understand that they belong to 2 different teams.