Nested file structure vs mapped drives !
I was wondering if there are any distinct advantages or disadvantages to using a nested file structure and restricting access and permissions, or use a load of mapped drives. If any one knows id be grateful if u would share this with me.
cheers in advance
cheers in advance
Mapped drives are fine, to a point, you have a finite number available to you.
I assume this is on a network of somekind? How many top level entry points do you have to have? Can you provide a point and allow people to drill down? What O/S are you using, if 2003 Server - look in to DFS.
I assume this is on a network of somekind? How many top level entry points do you have to have? Can you provide a point and allow people to drill down? What O/S are you using, if 2003 Server - look in to DFS.
nested file structure - easy to maintain.
mapped drives - easy to navigate.
You're best bet is to sort out the folder structure so that there is minimal traversal to find the files you want.
Create the structure based on function, not department. Look at what people DO, not who they work for.
Personally I avoid mapped drives - one for home, one for shared is all you really need.
Spend time getting the structure right will reap dividends.
mapped drives - easy to navigate.
You're best bet is to sort out the folder structure so that there is minimal traversal to find the files you want.
Create the structure based on function, not department. Look at what people DO, not who they work for.
Personally I avoid mapped drives - one for home, one for shared is all you really need.
Spend time getting the structure right will reap dividends.
Trending Topics
Thread
Thread Starter
Forum
Replies
Last Post




