This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
it:zoo:rhinomacdeployment [2017/05/04] |
it:zoo:rhinomacdeployment [2020/08/14] 127.0.0.1 external edit |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Distribuzione gestita di Rhino per Mac====== | ||
+ | > **Product: | ||
+ | > **Summary: | ||
+ | =====Question===== | ||
+ | We recently purchased a Rhino for Mac Education Lab License. What are some strategies to help deploy it configured to use a Zoo license server on several computers at our university? | ||
+ | |||
+ | We use [[http:// | ||
+ | |||
+ | =====Answer===== | ||
+ | Here is some helpful information. | ||
+ | |||
+ | 1) When you run Rhino for Mac for the first time, it creates the following folders: | ||
+ | |||
+ | / | ||
+ | / | ||
+ | |||
+ | Important: Each of these folders is **chmod** with **+rwx** so anyone can write information to it. | ||
+ | |||
+ | 2) The // | ||
+ | |||
+ | 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 in the // | ||
+ | |||
+ | If your deployment system performs steps 1, 2, and 3, besides pushing the Rhino application bundle into each system' | ||
+ | |||
+ | =====More information===== | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | |||
+ | \\ | ||
+ | |||
+ | {{tag> |