Network Share Naming Conventions

[wackjack]

Hello,

I have tried desperately to find a resource or paper online to no avail. What I am trying to do is find a couple different types of making share names. The bottom line here is that I'm trying to organize network data.

What would be the best/efficient way of doing that?

I appologize if I'm not making much sense. Maybe an example will help. One way we could do this is by: \\servername\department\project\<data>

or

\\servername\clients\<data>

Are there other efficient ways of organizing data on a network?

Maybe you could share how data is organized on your network. That would help me a lot.

Everyone's comments are welcomed and much appreciated.

 

[Philly44]

I'm sure a large amount of people will respond similar to this. Where I am we each our own personla shares mapped to \\servername\username, we have groups shares setup as \\servername\groupname. For the groups we setup groups in the AD and assign specific groups to specific group shares ie: GRP-FINANCE has access to \\servername\FINANCE . We also setup a common share at the groupname level so that people can share files without having to e-mail or burn them. As for Backing this up, we backup everything except the common share as thats really only meant as a temp folder for everyone to use. I this helps.

 

[Zelandakh]

shares like sharedfolder are accessed by \\servername\sharedfolder and NOT where they are located on that server.

I don't do shares for users - it is hard work.

Create a share called users. Shared to all with full access. Then under their AD home folder specify \\servername\users\%username% which creates the folder with the right permissions for them. No real admin required.

Then follow Philly's post for departmental shares.