I manage Rhino 5 Beta in an educational lab environment. We have three educational lab licenses which cover 90 seats across our various computer labs.
We typically create one new software image each year (or each semester is large changes are needed).
We use DeepFreeze to manage user accounts - students are able to make any changes they wish while they're logged into a computer, but the moment they log out, DreepFreeze resets the image.
This means that when we need to update Rhino 5 (about once a month) we have to individually unfreeze / install Rhino 5 update / re-freeze each computer.
This is pretty arduous. Does anyone know of a smarter solution for maintaining Rhino 5 Beta updates in an educational lab environment?
Thank you for your time.
The problem may be moot. The Beta process is essentially finished. We just released (3pm PDT), what we think will be the final release candidate. We will monitor problems for the next couple of weeks and if nothing critical comes up, this will be the code that the initial release of V5 for Windows will be using.
That's exciting to hear!
I've actually run out of validations for v5 while trying to update the labs - since our 90 seats are floating I thought we would be able to validate all of our labs (100+ machines) with no validation restrictions. The validation only affects the ability to use the next version, so for now it's just dealing with the annoying validation pop-up window, but I would like to fix this.
Please advise! And thank you!