+ Post New Thread
Results 1 to 6 of 6
Windows Thread, User area organisation in Technical; Can anyone think of good reasons not to have all students in one folder for their user areas? I know ...
  1. #1

    TechMonkey's Avatar
    Join Date
    Dec 2005
    Location
    South East
    Posts
    3,294
    Thank Post
    226
    Thanked 406 Times in 303 Posts
    Rep Power
    162

    User area organisation

    Can anyone think of good reasons not to have all students in one folder for their user areas? I know it will be a mass of 650 folders but I can't think of any reason off the top of my head that would need them divided up.

    Bit of background, we have a pre-school that then feeds into 2 different schools on site so the benefit to one heap of folders would be we wouldn't have to juggle areas around after the move between schools. Obviously they would be organised in AD.

    Part of me just feels it would be wrong but I can't find a reason why!

    Ta

  2. #2
    AJWhite1970's Avatar
    Join Date
    Sep 2012
    Location
    Wiltshire
    Posts
    341
    Thank Post
    92
    Thanked 77 Times in 59 Posts
    Rep Power
    17
    Potentially your AV client might slow things down trying to preempt the scanning of 650 folders off a root folder?

    #completeguess

  3. Thanks to AJWhite1970 from:

    TechMonkey (27th June 2013)

  4. #3
    ADMaster's Avatar
    Join Date
    May 2012
    Posts
    333
    Thank Post
    5
    Thanked 35 Times in 30 Posts
    Rep Power
    23
    To delete the leaving year groups folders without sifting through 650 folders to find the correct ones.

  5. Thanks to ADMaster from:

    TechMonkey (27th June 2013)

  6. #4


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,651
    Thank Post
    275
    Thanked 780 Times in 607 Posts
    Rep Power
    224
    Off the top of my head......

    You'd have to be more cautious when scripting and look at the foldername to determine whether that was a student you need, as opposed to splitting shares by yeargroup.

    On the other hand, having a universal "homedir = \\server\share\%username%" (or \domain\dfsroot\share\%username%) would make config files and other scripts easier to maintain.

    If you were migrating a server via DFS-R, you couldn't push a yeargroup over at a time and you may run into "hey I'm doing reasonably heavy replication in the working day" issues. That's mostly a case of ensuring you throttle appropriately when people are using stuff.

    Being able to quickly assess "OK, Y7s are using this much, Y8 are using...." for capacity planning would take longer, but it's infrequent.

    Quotas can be set on a "who owns that file?" basis, so that's not really an issue.

    I'd test that it doesn't impact performance for file access/restore and ACL enumeration/modification. How many files and folders are we talking about?

  7. Thanks to pete from:

    TechMonkey (27th June 2013)

  8. #5

    TechMonkey's Avatar
    Join Date
    Dec 2005
    Location
    South East
    Posts
    3,294
    Thank Post
    226
    Thanked 406 Times in 303 Posts
    Rep Power
    162
    Thanks all. I knew there were reasons just couldn't put my finger on them. Leavers is the bigun but per year scripting and replication are good as well.

  9. #6


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,647
    Thank Post
    229
    Thanked 865 Times in 743 Posts
    Rep Power
    297
    you could start your usernames with a number denoting tear of entry/exit then all year x would be together even if its in 1 big folder

SHARE:
+ Post New Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •