Not that this helps, but our Library IT group has found that Deep-freeze causes all kinds of problems including blocking popups at the user level that would have identified a problem with Pharos. That one cost us a week of testing.
One possible answer would be to use a partition to store the user data and then run a log off script that blows away the data on that partition, that way each time the user logs off, the data they created is cleared. Since the log off script should run using the generic users credentials, it can only delete the data and not any system or app files.
Thanks for the suggestion. Fortunately, at this stage, we’ve not had issues with DeepFreeze from that perspective (we have from a couple of others, but that’s a different story). DeepFreeze is quite merrily doing the job we wanted of it – resetting any user data, installs etc. that a user may have done – when the machine reboots.
It’s getting it to reboot (which is easy enough), and then log back in (not so easy), which is the issue for us – we want to have patrons have minimal down-time, so they are more likely to use the machines… but we also need to do our best to protect their privacy, among other things.
We could remove the Pharos GINA, and have Windows auto log the machines in… but then they wouldn’t be “managed”, making them more difficult to support.
Application Support Officer
City of Gold Coast
T: 07 5581 7513 M: 0414 180 233
PO Box 5042 Gold Coast Mail Centre Qld 9729