The lab version for schools is designed exactly for this situation.
The installation is managed entirely by the school, including updates. There are a few ways this is done.
Method 1 - deep freeze
- Using an "image" of the school lab-machine installation
- The image is updated each day, via script, to check for Fusion updates
- The image is deployed each day to the school computer labs
- Benefit: The students can run Fusion at home on personal machines, using the latest build, and the school computers will be able to open these files.
Method 2 - manual install and update
- The school computers are imaged or installed with the educational admin installation
- When an update is available (several times a year) the school computers are updated by re-installing, or updating the installation.
- Risk: unless the school computers are always up to date, the students can run Fusion on personal machines that have newer up-to-date installations and create files that cannot be opened at school. This is very disruptive.
Method 3 - normal streaming update
- This is what you have, according to your description.
- Fusion is updated several times a year.
- Students accept the update when they start Fusion
- After a few minutes the update is downloaded and they restart Fusion
- Benefit: students using school computers and personal computers will always be in sync, the update is very easy to manage (just click download/restart when done), and the school IT department doesn't need to monitor for updates (method 2), or use deep freeze (method 1).
Phil Eichmiller
Software Engineer
Quality Assurance
Autodesk, Inc.