| T O P I C R E V I E W |
| librarytech |
Posted - 06/29/2012 : 11:46:17 AM
I haven't tried any of this yet, but before I do I have a question. If a public user chooses Windows 7 instead of Rollback Windows on the boot screen, does this write the changes that have been made to the frozen image or just let them work within the changes while still preserving to option to roll back to the original state later. I don't want the public to have any shot at writing permanent changes and some of them will try anything on a computer. Thanks for any help. This is for a public library system and computers can get trashed in a hurry without protection. |
| 1 L A T E S T R E P L I E S (Newest First) |
| Pesos |
Posted - 06/30/2012 : 5:12:18 PM
Windows 7 is just the normal boot, which means changes will continue to be written to the snapshot (the master VHD will remain untouched). You can boot this way countless times and the original master will still be available to roll back to.
In order for someone to write changes to the master, they have to:
1) add a file called "noauto.txt" to the root of a physical disk
2) select rollback from the boot menu
3) type "merge" and confirm when the command prompt comes up
If they perform #2 without having done #1, then they will simply cause a rollback to the master (no big deal).
You can prevent most users from being able to perform #1 (even if they somehow read up on SS and learned that was what to do) by using the registry to hide drive D (the only likely physical disk that will be available) - I have done this in our lab and it works great... |
|
|
