Possibly, maybe I'm over reacting. But I wourld rather not allow students to trawl around the hard drive and other drives. Plus it opens up the possibility of saving work in random places that won't be specific to the user, won't be backed up and that we will have to chase down.Originally Posted by OutToLunch
Also it just grates a little that we don't have any other programs that cause this problem.
This is the best approach. I'd like to know what are the best practices for setting file permissions for students windows drive, especially for terminal servers. Clearly removing write perms should be done - but what about all the read/execute within the windows partition ?PostPosted: Fri May 18, 2007 9:42 am Post subject: Re: Scratch
If your file permissions are set up right, surely it doesn't matter what they can see? Regardless of what magic dialogue it provides for viewing things, it's still running under their user and Windows will still hold the app and any file handles it opens to their permissions...
There are currently 1 users browsing this thread. (0 members and 1 guests)