Right then, so it would seem that staff have completely forgotten how to use the folder structures on the network here (either that or they don't give a .....) so I'm just wondering how anal I get about telling them about the drive structure again.
I've written out a "this is what each person sees" with a Student and Staff list, but it's 2 pages of A4 an I doubt anyone will actually pay any attention to it, so how do you explain about the drive structure? Do I put a note up saying "I've noticed a lot of files are being saved incorrectly on the network. Please see me if you do not understand the folder structure" thing then, if they come to me, give them the 2 sheets of A4 with a brief chat about how the files should be stored etc? Do I request a staff meeting to go over the drive structure and even give them chance to think of something better if they feel they have particular needs that aren't being met?
Rule of thumb here we have Students who get a My Documents and a Class Share (so each class has it's own shared folder to make it easy for staff to place files available for each child). Staff get a My Documents, Staff Share, Scanned Docs folder (from our MFPs), Access to all the class shares for the students and Clicker SuperDrive. Both sets also have a shared folder where they can put photostories and such that they want putting on the reception screen, though that is more of a legacy thing now which I'll probably get rid of. Obviously there are exceptions (admin drives for SIMS etc) but that's generally how it works.
So just wondering how to explain they shouldn't be storing any pupil data on the drives the pupils can access etc.
How do you guys go about it.
Draw a "pyramid" of the data structure with the pupil's folders at the bottom and a honking great line across the pyramid explaining that EVERYTHING below the line can be seen by the pupils.
They'll still ignore it, but at least you can say that you made it easy to understand!
Force them using groups and ntfs permissions?
Edit: Though having said that, I can stop the renaming of folders and saving outside of the folder structure I guess .. lol ..
Last edited by soveryapt; 24th September 2013 at 01:11 PM.
That's the ticket.
We have a staffonly drive and a public one not to say that stuff that shouldn't be there doesn't get put in public but it's 2 distinctly separate areas then.
If they don't understand a hierarchical directory structure now (from the 1960's? 70's?) they probably never will.
Why not just accept it doesn't work and move onto search and labeling instead?
Your directory structure does appear overly complex.
You could reduce the error rate a bit by using access based enumeration*, but I'd aim for a leaner set of shares.
*say I teach GCSEHistorySet02, ASHistorySet03, A2HistorySet01 and those sets are created as security groups in AD (kids + people who teach them) and folders in \\server\classes.
In \\server\classes I'd only see the 3 folders for the classes I teach and the kids would just see their subject classes.
Edit: DFS doesn't support access-based enumeration properly until Server 2008 or greater.
There are currently 1 users browsing this thread. (0 members and 1 guests)