Pau Lo
asked on
NTFS grey tick
Ok... heres the scenario.
We have a departmental share. \\server\share.
Within that each team has their own directory which DOES NOT inherit the root permissions of the share. Each teams directory should have an ACL specific to the team. Some of the teams directory ACL's have not been set correctly.
Our teams directory was set to just limit access to us and our IT support. Unfortunately one of our users managed to drag it into another teams directory. It was located, and moved back to the root of the share.
However, I just checked the NTFS on our directory ACL and its not what it was before.
So;
question 1 - if you move directory purposely or unintentionally from root of a share, to inside another teams directory, then move it back. Does it scoop up the ACL from within that other teams ACL. As thats what seems to of happened.
question 2- what does a grey tick next to an NTFS ACL option represent. For example, our group has solid black ticks next to the various NTFS options, but theres another group on their, with a grey faded tick next to the NTFS ACL options. Just wondered if thats relevant.
We have a departmental share. \\server\share.
Within that each team has their own directory which DOES NOT inherit the root permissions of the share. Each teams directory should have an ACL specific to the team. Some of the teams directory ACL's have not been set correctly.
Our teams directory was set to just limit access to us and our IT support. Unfortunately one of our users managed to drag it into another teams directory. It was located, and moved back to the root of the share.
However, I just checked the NTFS on our directory ACL and its not what it was before.
So;
question 1 - if you move directory purposely or unintentionally from root of a share, to inside another teams directory, then move it back. Does it scoop up the ACL from within that other teams ACL. As thats what seems to of happened.
question 2- what does a grey tick next to an NTFS ACL option represent. For example, our group has solid black ticks next to the various NTFS options, but theres another group on their, with a grey faded tick next to the NTFS ACL options. Just wondered if thats relevant.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks KCTS - I am not sure on the "transfer mechanism", be it by a copy or a move.
But whether it be a copy or a move, if I wanted to copy \\server\share\dir to within \\server\share\dir2 I'd need write(?) permissions to either copy or move that file into that location wouldnt I?
Just trying to tie down who moved our folder via seeing on that ACL who could have done so.
But whether it be a copy or a move, if I wanted to copy \\server\share\dir to within \\server\share\dir2 I'd need write(?) permissions to either copy or move that file into that location wouldnt I?
Just trying to tie down who moved our folder via seeing on that ACL who could have done so.
ASKER
PS _ it was moved on the same partition not onto a different one. What I wondered though is if its moved to a sub dir, those on the parent directory, if they have full control - cant they just apply the parent permissions to anything in its child folders - this wiping out all the more restrictive child permissions? I assume if they didnt have full control they could do this, but if they did they could.
So if moved from A to B on the same volume, B has very open ACL, but as A was moved on the same volume, just as users can access \\server\share\B doesnt automatically mean they can access \\server\share\B\A
So if moved from A to B on the same volume, B has very open ACL, but as A was moved on the same volume, just as users can access \\server\share\B doesnt automatically mean they can access \\server\share\B\A
ASKER