Everyone and NTFS permissionsNTFS permissions weird inheritance (second take!)Windows Share Permissions VS NTFS PermissionsAD security group with one user is, seemingly, being ignored in favor of Domain UsersShare folder read permissions for everyone and ntfs write for local group?Is there a way to give NTFS file permissions to users from other Windows installations?Grant all NTFS permissions to a security groupNTFS Folder Permissions
How to use stat(1) or Bash to check whether FILENAME refers to a file
Confusing Nest function behavior
What was this pickled vegetable which I was served at a middle eastern restaurant (description inside)?
Why is this negated with nicht and not kein?
Will practicing on an Ipad hurt my playing?
Finding how much time it takes for a complete Earth revolution around the Sun
Sold item on eBay, buyer wants it to be delivered to another country, and pay by bank transfer
Decode the Dreaded Alphabet Cypher™️
Organising child care when giving birth
Selecting Primes from list of list
Pay everything now or gradually?
Rite of Winter: How to Stop Crescian Couples from Mutual Assassination
Why is the sample variance of a Sample Average Approximation calculated in this way?
My time machine can go back farther than yours -- why?
How did the star tracker on the Corona (Key Hole) satellite work?
Are these pigtails inside the panel and outside a junction box allowed?
Is it possible to write Quake's fast InvSqrt() function in Rust?
Possible way to counter or sidestep split-second spells (like Trickbind) in a particular situation
How to negate forall?
Mixing 3.5 hdd and 2.5 hdd in LSI RAID 1
How do you say "to play Devil's advocate" in German?
Character Development - Robert Baratheon
Rock/Mineral Ore Eating Organism
Why is/was the National Liberal Party of Romania opposed to Catholic & Hungarian school when they support a German-minority president?
Everyone and NTFS permissions
NTFS permissions weird inheritance (second take!)Windows Share Permissions VS NTFS PermissionsAD security group with one user is, seemingly, being ignored in favor of Domain UsersShare folder read permissions for everyone and ntfs write for local group?Is there a way to give NTFS file permissions to users from other Windows installations?Grant all NTFS permissions to a security groupNTFS Folder Permissions
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I have been reading some articles about file sharing permissions. In most of the articles it states that the easiest way to manage share and NTFS permissions is to grant everyone full access and then use NTFS to further restrict permissions.
My only question is...
What happens if a user is in the everone group but not in the NTFS security group. Will that user have full control?
regards
windows ntfs shared-folders windows-server sharing
add a comment
|
I have been reading some articles about file sharing permissions. In most of the articles it states that the easiest way to manage share and NTFS permissions is to grant everyone full access and then use NTFS to further restrict permissions.
My only question is...
What happens if a user is in the everone group but not in the NTFS security group. Will that user have full control?
regards
windows ntfs shared-folders windows-server sharing
add a comment
|
I have been reading some articles about file sharing permissions. In most of the articles it states that the easiest way to manage share and NTFS permissions is to grant everyone full access and then use NTFS to further restrict permissions.
My only question is...
What happens if a user is in the everone group but not in the NTFS security group. Will that user have full control?
regards
windows ntfs shared-folders windows-server sharing
I have been reading some articles about file sharing permissions. In most of the articles it states that the easiest way to manage share and NTFS permissions is to grant everyone full access and then use NTFS to further restrict permissions.
My only question is...
What happens if a user is in the everone group but not in the NTFS security group. Will that user have full control?
regards
windows ntfs shared-folders windows-server sharing
windows ntfs shared-folders windows-server sharing
asked Sep 20 at 14:24
user944413user944413
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
There are 2 different aspects of accessing files on a share.
The share itself (which is like a door), and the files behind it, which is like the room.
By setting accessrights to the share itself, you only set permissions if a user can go through the door or not. In the past, this was the only way to set access to files on a network and for the sake of backwards compatibility, this was never removed.
For that reason, it is indeed common practice to give the Everyone group Full Control on the share itself.
When you then set access rights in the Security tab, you control access per file or per folder inside the share. For example, you can specify that a user can go through the door and reach the room behind it and the user only has permission to sit at table 2 and 3 (aka different folders controlled by either security groups or the user has permission set on the folder directly.
So if you give the Everyone group full control on the share, but you set NTFS security group rights, the user can still be denied.
If however you set the Everyone group in the security settings alongside with an NTFS security group, everyone has full control and the security group is ignored.
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "3"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1484616%2feveryone-and-ntfs-permissions%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are 2 different aspects of accessing files on a share.
The share itself (which is like a door), and the files behind it, which is like the room.
By setting accessrights to the share itself, you only set permissions if a user can go through the door or not. In the past, this was the only way to set access to files on a network and for the sake of backwards compatibility, this was never removed.
For that reason, it is indeed common practice to give the Everyone group Full Control on the share itself.
When you then set access rights in the Security tab, you control access per file or per folder inside the share. For example, you can specify that a user can go through the door and reach the room behind it and the user only has permission to sit at table 2 and 3 (aka different folders controlled by either security groups or the user has permission set on the folder directly.
So if you give the Everyone group full control on the share, but you set NTFS security group rights, the user can still be denied.
If however you set the Everyone group in the security settings alongside with an NTFS security group, everyone has full control and the security group is ignored.
add a comment
|
There are 2 different aspects of accessing files on a share.
The share itself (which is like a door), and the files behind it, which is like the room.
By setting accessrights to the share itself, you only set permissions if a user can go through the door or not. In the past, this was the only way to set access to files on a network and for the sake of backwards compatibility, this was never removed.
For that reason, it is indeed common practice to give the Everyone group Full Control on the share itself.
When you then set access rights in the Security tab, you control access per file or per folder inside the share. For example, you can specify that a user can go through the door and reach the room behind it and the user only has permission to sit at table 2 and 3 (aka different folders controlled by either security groups or the user has permission set on the folder directly.
So if you give the Everyone group full control on the share, but you set NTFS security group rights, the user can still be denied.
If however you set the Everyone group in the security settings alongside with an NTFS security group, everyone has full control and the security group is ignored.
add a comment
|
There are 2 different aspects of accessing files on a share.
The share itself (which is like a door), and the files behind it, which is like the room.
By setting accessrights to the share itself, you only set permissions if a user can go through the door or not. In the past, this was the only way to set access to files on a network and for the sake of backwards compatibility, this was never removed.
For that reason, it is indeed common practice to give the Everyone group Full Control on the share itself.
When you then set access rights in the Security tab, you control access per file or per folder inside the share. For example, you can specify that a user can go through the door and reach the room behind it and the user only has permission to sit at table 2 and 3 (aka different folders controlled by either security groups or the user has permission set on the folder directly.
So if you give the Everyone group full control on the share, but you set NTFS security group rights, the user can still be denied.
If however you set the Everyone group in the security settings alongside with an NTFS security group, everyone has full control and the security group is ignored.
There are 2 different aspects of accessing files on a share.
The share itself (which is like a door), and the files behind it, which is like the room.
By setting accessrights to the share itself, you only set permissions if a user can go through the door or not. In the past, this was the only way to set access to files on a network and for the sake of backwards compatibility, this was never removed.
For that reason, it is indeed common practice to give the Everyone group Full Control on the share itself.
When you then set access rights in the Security tab, you control access per file or per folder inside the share. For example, you can specify that a user can go through the door and reach the room behind it and the user only has permission to sit at table 2 and 3 (aka different folders controlled by either security groups or the user has permission set on the folder directly.
So if you give the Everyone group full control on the share, but you set NTFS security group rights, the user can still be denied.
If however you set the Everyone group in the security settings alongside with an NTFS security group, everyone has full control and the security group is ignored.
answered Sep 20 at 14:29
LPChipLPChip
40.4k5 gold badges59 silver badges94 bronze badges
40.4k5 gold badges59 silver badges94 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1484616%2feveryone-and-ntfs-permissions%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown