Hi,
Apolgies for the somewhat long question, but I would appreciate some help please. I have been reading various Technet articles, but I am still unclear, I am somewhat (OK very!) confused about setting the permissions for DFS shares. I think I'm being bitten by interaction between share permissions and permissions on the DFS folders.
Say I want to have one storage volume directory as the repository for all of my DFS fileshares
e.g, G:\DFS
This path will contain a mixture of shares, some public, some private, obviously the users should not be able to use the private areas. When I set this up, it was created as a share on the server, thinking that I didn't want users to be able to delete files they shouldn't, I set this up with everyone as READ ONLY and Administrators as FULL CONTROL. I planned on using Access Based Enumeration to hide the directories that the users could not modify.
The first problem is that I think that the share permission in overriding anything that I do at a lower level in the tree when I try to set premissions to WRITE on lower level directories. I think that making the share R/W for all users would help this, but it just "feels" wrong. If I give everyone FULL control on the share permission, am I opening things up too much?
OK, here's the first question.......
Do I really need to share G\DFS at all, or can I just share the appropriate directories below it?
Will "unsharing" G:\DFS have any adverse effects?
Now, say I want :-
G:\DFS\Public ( a "root" folder with a mixture of R and R/W directories)
e.g.,
G:\DFS\Public\RO (Read only for all accept administrators)
G:\DFS\Public\RW (R/W for all)
Can I have both RO and R/W below the Public share?
A similar question for the users directories
G:\DFS\Users\
G:\DFS\Users\user1
G:\DFS\Users\user2
The users should just see their own share, but have full control on it
regards
Dave
Dave