asked on

Network Share folder structure suggestions

I am in the process of developing and implementing a new network shared folder structure. The current is way out dated, and all over the place. This will do two things, structure the folders themselves, and straighten out the permissions.

I have the groups laid out and permissions will not be a problem. My question is regarding best practices or best starting layout for a network shared folder. Here is what is currently planned.

Drive H = User home folders (not a problem)
Drive P = General Network Share

Accounting
Executive
HR
IT
Sales
Service
All
Accounting
Executive
HR
IT
Sales
Service

Root department folders will be accessible only by their respective departments. Departments under ALL will have folders visible and/or editable to all as well as folders visible and/or editable to some. There will be more miscellaneous folders under all for groups that need them. My question is: Is this a good way to structure the folder. Is there a better base structure to use? This is simply what I have been used to, but have not found any decent resources regarding a good best practice for setting up the folder structure.

Thanks for any input you may have

Javedtariq

I would suggest to use the following approach which we have at work.
This will make it easier for your support staff and new starters to understand it quickly .

All our security groups in AD start with specific letters according to the function of the group . for example
For distribution groups we use "_three letters for department and then distribution list name " e.g. for customer services distribution list it will be _CSD_All_Agents

For Permissions to Folder all the group start with SH (shares) e.g. access group to a share will be called SH-CSD-TECHNICAL-INFO-RW
SH - CSD - Technical Info - RW
SH shows that this is a share
CSD shows the department
next bit shows folder name
RW shows what kind of permissions they are.
We also have access groups with permissions to applications and internet resources they start with
AC like AC-INTERNET
Now as far as the folder structure is concerned this group naming style also applies on folders too.
Your root folders can be named on the name of the department but any sub folders should be created with three letter conventions e.g.

Accounting/ACC-Annual-Reports
Accounting/ACC-Staff-Performance
There are actual two groups we have for every root folder one with read only permissions and one with read and write permissions

_CSD_xxxxxxxx
_CSD_xxxxxxxx
_CSD_xxxxxxxx
This is the format for Distribution list

SH-CSD-TECHNICAL-INFO-RW
SH-CSD-xxxxxxxxxx-RW
SH-CSD-xxxxxxxxxx-RW
SH-CSD-xxxxxxxxxx-RW
This is the format for shares

AC-INTERNET
AC-Application name
AC-Application name
AC-Application name
Access Groups

Then we have a script, which according to their OU maps there root folders for them.
So when creating a new user all we have to do is put them in right OU which is their department name and they get the right drives .

I hope this will help you a little bit if not exactly what you are looking for .

BHForum

ASKER

Thanks, Javedtarig. I was probably not very clear on my needs. I have the permissions and groups setup without a problem. It is the folder structure itself that I am looking at. Primarily, the folder tree structure for department only shares, and for departments to share with all others. In other words, should I have the structure that I listed above:

Accounting
Executive
HR
IT
Sales
Service
All
Accounting
Executive
HR
IT
Sales
Service

Or something more like this:

Accounting
Acct-Only
Shared
Executive
Exec-Only
Shared
HR
HR-Only
Shared

Etc.

Hope that clarifies.

Thanks

ASKER CERTIFIED SOLUTION

Javedtariq

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

BHForum

ASKER

Javedtarig, your recommendation is pretty much what I had in mind. The structure of:
Executive
Exec-Only
Shared
HR
HR-Only
Shared

was more for illustration. It was a structure different than the previous, where the department only area was on the root level, then a folder called ALL would have the department folders containing shared information. I think a single level of folders will make for easier navigation without making administration more difficult. Folders to be shared outside of the department will be removed from inherited permissions, therefore allowing any new folders created to be deparment viewable only until IT changes those permissions explicitly.

Thanks for helping me air out and get things more clear.