V6 WIP licensing in a Zoo environment

[dale (Dale Fugier)]

Hi Alex,

I will try my best answer all of your questions.

@AlexYau

What is the recommended way for a Zoo licensed environment to allocate WIP licenses?

The first thing you want to ask yourself is how many of your users should be looking at the Rhino WIP. Keep in mind this is “Work in Progress” software. It is not Beta software. And, we are still fairly early in the WIP process.

Once you’ve determined this, you can download the WIP on their behalf (if you are not willing to share Rhino 5 license keys with them.)

Rhino WIP license keys are not tied to a computer in any way. So there is no problem with one person acquiring all of the Rhino WIP license keys and then distributing them to whomever need them.

@AlexYau

Like the Rhino5 WIP, the v6 WIP requires, online activation for each install instance.I assume, like the v5 WIP, too many activation on the same license results in a lock out.

Yes, this true.

@AlexYau

Documentation of the msi deployment command line switches for the WIP msi

http://wiki.mcneel.com/rhino/installingrhino/5.0

@AlexYau

Re-establishment of offline activation - the current binary points to the V5 activation site, which won’t accept keys starting with RH6B

We’ll get there. Like I said, we are pretty early in the WIP process.

@brian can you look info this?

@AlexYau

Zoo based network licensing, so I don’t have to track which machines are allocated to which keys.Dale has mentioned a new version of Zoo would be required.

Yes, a Rhino WIP-compatible version of the Zoo is coming (too).

@AlexYau

A Zoo server that doesn’t insist on port 80.

This is on the wish list.

http://mcneel.myjetbrains.com/youtrack/issue/ZO-37

@AlexYau

I recall not being aware of Zoo5 until very late in the V5 Beta process.

If I recall correctly, Zoo 5 was available fairly early in the Rhino 5 WIP process, as we wanted extensive field testing before shipping.

@AlexYau

The lack of any way to specify the Zoo server as parameter in the MSI install was another oversight.

You can specify the name of a Zoo server as part of a scripted Rhino install.

http://wiki.mcneel.com/rhino/installingrhino/5.0

@AlexYau

Thankfully, setting the registry key by AD policy to point to the

You can also (just) use DNS.

http://wiki.mcneel.com/zoo/findzooserver

Let me know if I’ve missed anything of if you have further questions.