afrend
asked on
Share permissions Server 2016
Migrating to Server 2016. The server in question is both the PDC and file server, two partitions, C and D.
D partition has the default share of D$, and this is where shares will be created from the folder tree located there.
The problem is that I can create shares all day long, with custom permissions, but the default attribute on any folder created inside of D$ is Read Only. The vendor states that it is because I created the shares via Computer Management and not the Share Wizard. Used the Share Wizard, same result.
Some articles state that this is a "default attribute" and that's just the way it is. Others suggest a command line permissions adjustment, using
ATTRIB -R /D /S "<Foldername>
or
attrib -r -s c:\test
Neither solves the problem, at least not according to the GUI. I can't believe this to be the "way it is" because a read only shared service wouldn't work very well, and this problem has been around since Server 2008. My best guess is that unlike what I am used to, the Read Only attribute means nothing, and the share permissions over ride the folder attributes.
Yes or no? I can't really roll out a new server and domain to the users as a read only kernel. Am I missing something here?
Thanks.
D partition has the default share of D$, and this is where shares will be created from the folder tree located there.
The problem is that I can create shares all day long, with custom permissions, but the default attribute on any folder created inside of D$ is Read Only. The vendor states that it is because I created the shares via Computer Management and not the Share Wizard. Used the Share Wizard, same result.
Some articles state that this is a "default attribute" and that's just the way it is. Others suggest a command line permissions adjustment, using
ATTRIB -R /D /S "<Foldername>
or
attrib -r -s c:\test
Neither solves the problem, at least not according to the GUI. I can't believe this to be the "way it is" because a read only shared service wouldn't work very well, and this problem has been around since Server 2008. My best guess is that unlike what I am used to, the Read Only attribute means nothing, and the share permissions over ride the folder attributes.
Yes or no? I can't really roll out a new server and domain to the users as a read only kernel. Am I missing something here?
Thanks.
An "old new thing". Just disregard it, the checkbox has no meaning in this case.
ASKER
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK. Any idea why it is that way? Just curious.
https://support.microsoft.com/en-gb/help/326549/you-cannot-view-or-change-the-read-only-or-the-system-attributes-of-fo answers that, it applies to all windows OS'.