Have a client with 20+ V8 licenses in a LAN Zoo - some of which are also upgrade licenses going back version by version to Rhino 4 or 5 - and they are wanting to move all that to a new Zoo server. Is there any kind of automation to do this?
I asked them how they identified the current Zoo on the local installations, via Zoo name or IP address and they answered “neither” - the IT guy said they use an “alias” - which I have no idea what that is or how it actually works (he says it’s more “robust”).
Is there any other solution besided ‘manually’ transfering each individual license key tree (keys of all the upgrades to the latest version) one-by-one for each of the 20+ licenses? The objective here is not to put the users out of work for too long…
Moving a Lan Zoo is essentially like installing from scratch. They will need to remove all the licenses and add them back in. If they run into any issues adding these to the new server after removal have them contact sales.
With no complications in the license release - revalidation process it should go quick and can be done concurrently while the original Lan server is running. If they want to schedule a time we available to help if need be.
It is not possible to have a license in two LAN Zoo servers at the same time.
If a license is in use, you will not be able to remove it. Use the LAN Zoo’s Recover option if you can verify a license is not in use, but still displays checked out. Be aware this will close down any Rhino that has this license in use.
So basically they need to tell all their users to quit Rhino during the procedure - otherwise the licenses will not be able to be removed from the old Zoo.
OK, so it will be possible to for example just install V8 on the new server - will it ask for the V7 associated with it to validate? But I assume that the previous version licenses will still need to be removed from the old server in any case?
I don’t know if they are using V7 anymore, it might be possible, I will check.
Yup, removal of the license chain completely from the old server is required. Once it is clear then they can add just Rhino 8 if that is all they need.
The trouble comes up on old validations of Rhino 4 & 5 where there was a different email at some point (before they put it on the lan). That is where we might need to help clean things up.
if they want to speed up the process, they can call sales, have them wipe all their validations on the old server manually from our end in one go- (that only take a few seconds to do each one) which will save time having to remove them themselves.
this will make all their licenses “moveable” and they can then start adding them to the new zoo.
with this as the “nuclear option” it insures that nothing gets stuck on the old server (which is what causes delays getting up and running again) and should make the installation on the new server quick and smooth as any potential conflicts will be pre-mitigated.
they do not need to reinstall anything they are not using anymore (i.e v3 or 4…)
If they do this, they will want to do it when no one is using rhino.
Yep - “therein lies the rub” as they say… Busy high-end watch company with multiple semi-independent design labs and users - hard to get everyone on the same page.