From what I understand Share permissions do not replicate. At one point MS was pushing one way replication with DFSR. You would prevent replication on one end using share permissions. AFAIK they have backed off one way replication because there were too many problems.
hth DDS
"Andrea Casini" <AndreaCasini[ at ]discussions.microsoft.com> wrote in message news:0ED48689-554F-46F2-8B57-22CD7815A634[ at ]microsoft.com...
[Quoted Text] >I agree that everything could be handled via NTFS Permissions, i was just > wondering if i was doing something wrong, if something was wrong with my > infrastructure or if DFS simply can't handle share permissions on folders > spread over the namespace. Thanx for the reply, anyway. > > Anybody else? > > "Joseph Daigle" wrote: > >> "Andrea Casini" <AndreaCasini[ at ]discussions.microsoft.com> wrote in message >> news:BD4C5D87-3814-4EAC-BFBA-901EC1136AAA[ at ]microsoft.com... >> > Hi, >> ...snip >> > Any idea why? What is the right way to operate a change on a share >> > permission if that folder is being replicated and share on many servers >> > with >> > DFS? >> >> Others might also agree with me here, but usually I don't touch actual >> share >> permissions. Typically, if it's going to be a read/write share I give >> "Everyone" "Full Access" to that share. From there I handle all >> permissions >> via NTFS. It's a lot easier because those permissions are replicated and >> I >> don't have worry about which server has which permission set. I suppose >> you >> could make an argument for "read-only" servers. But in that case you >> don't >> want the share permissions replicating. >> >> Hope this helps, >> >> -- >> Joseph Daigle >> >>
|