Let me point out a few things and see if this helps you in any way.
1.) When you run Rhino the first time, it creates the following folders:
/Library/Application Support/McNeel/Rhinoceros/License Manager
/Library/Application Support/McNeel/Rhinoceros/License Manager/Licenses
Important: each of these folders is
+rwx so any user can write information to it.
Rhinoceros/License Manager/Licenses folder contain’s Rhino’s license file, which for Rhino for Mac is named
781b000c-8d0b-4ed3-8ead-213bdb848f39.lic. For standalone licenses, this file is encrypted, unreadable, and unique per system. For network licenses, though, this file is clear text, readable, and can be moved between one system and another.
3.) For systems that have a network license, you will also find a
LicensesZooClient.settings file that exists in the
Rhinoceros/License Manager folder. This file is also clear text, readable, and can be moved between one system and another. It contains the name of the Zoo server as entered into Rhino.
If your deployment system can also performs steps 1, 2, and 3, in addition to pushing the Rhino application bundle into each system’s Applications folder, then you should be able to deploy Rhino to all 200+ systems.
For more information on how Rhino for Mac finds a Zoo server, see the following:
Does this help?