Hi, my company carries a couple hundred Rhino v5/v6 licences which are managed using Zoo
We are about to start planning our deployment of v6 using SCCM, which we also did previously with v5 and its updates and service releases.
Moving forward with v6 we are contemplating allowing the auto upgrade feature in v6, as we have really struggled keeping the 1000+ machines up to date with v5
I noted that there is an update frequency option for Service Release and Service Release Candidate. I guess these are ‘production’ and ‘beta’ releases?
Are local administrative rights required to download these?
If the user downloads the beta and finds there are issues with the build, is there an automated rollback process, or it’s a case of manually uninstalling and reinstalling the previous stable build?
In terms of packaging up Rhino v6 and future SR’s. How often are these released, every 2 – 3 months?
If we decide to carry on deploying Rhino updates via SCCM, are we able to turn off the update feature meaning our Rhino users cannot manually upgrade to either Service Release or Service Release Candidate
Thanks’ in advance