• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 390
  • Last Modified:

NTFS and Access Based Enumeration Issue

We are migrating from a Novell file server to Windows Server 2012 R2.  We are having issues with folder and subfolder permissions.
We have a top level folder that is shared, D:\FileShare.  Under FileShare we have a domain folder (Data), a user home folder (Users), a shared folder (Shared) and a private folder (Private).
\\Server\FileShare - Main shared folder with ABE
Net Use L:\ \\Server\FileShare
Folders under FileShare:
Data - Domain Users - Modify
Private - Administrators only, specific users. Private\SubFolder - specific user
Users - Administrators only.   Users\UserName - UserName - Modify
Shared - Domain Users - Modify
For Users, the main folder's permissions are only Administrators have rights.  The subfolders for each user, the UserName has Modify rights to that folder.  By doing this, when a user goes to \\Server\FileShare, they only see Data, Shared, and Private.  We do a drive mapping for users to access their home folder (net use H: \\Server\FileShare\Users\%UserName%).  
Where we have a problem is with the Private folder.  Only certain users will have access to this folder and subfolders.
Right now Private has only administrator rights.  Under Private are folders Group1, Group2 and Group3 for testing purposes.  For Private\Group1, this folder I gave my test user rights to it.  So they can use Windows Explorer and go to the path \\Server\FileShare\Private\Group1 and that user can see all the subfolders and files in it.  I then gave Group2 administrator only rights and created a subfolder (DivA) and gave the test user full rights to that folder.  However when the user goes to \\Server\FileShare\Private\Group2\DivA I get a Windows cannot access folder error.
Test User:
\\Server\FileShare\Private - denied
\\Server\FileShare\Private\Group1 - access
\\Server\FileShare\Private\Group2\DivA - no access even though user has full rights to DivA
This poses a huge problem for us because a user may only need access to DivA only and not see all the other files and subfolders of Group2.  
Group1 folder has three subfolders: G1DivA, G1DivB, and G1DivC
Group2 folder has three subfolders: G2DivA, G2DivB, and G1DivC
Group3 folder has three subfolders: G3DivA, G3DivB, and G3DivC
I have two users, John and Bob.  John needs access to Group1 and Group2 and all subfolders but not Group3.  Bob only has rights to Group2\G2DivB and no other folder.  
John has no issue accessing \\Server\FileShare\Private\Group1 and \\Server\FileShare\Private\Group2.  If John tries to go to \\Server\FileShare\Private he gets a network error.  If I add Domain Users with List Folder Contents to Private, John can see all three folders, even though he only has rights to Group1 and Group2.  John cannot access Group3, however we do not like the fact that he is aware that the folder exists.
Bob, on the other hand cannot access G2DivB even if he goes to the UNC path of \\Server\FileShare\Private\Group2\G2DivB.  I could add Domain Users with List Folder Contents so that they can traverse through the folders to get to the one they do have access to, however we believe that is a security issue for users to see folders they do not have access to.
If I give Domain Users just Traverse Folder rights, they don't see any folders.  If I give just List Folder in advanced permissions, they don't see any folders.  They only way I can get them to see folders is the List Folder Contents permission.
What permissions do I set so that when Bob wants to go to the G2DivB folder, when he goes to Private he only sees Group2 and not Group1 and Group3, and when he goes to Group2 he only sees G2DivB and not G2DivA and G2DivC?
  • 2
1 Solution
Go to server manager and navigate to Files and storage services\Shares and go to share folder properties, and enable "enable Access Based enumeration"

This will ensure that user will see only those folders for what he has access
DamonVanAuthor Commented:
I should have posted this along with the original post but I didn't.

I'm coming from a Netware environment migrating to a Windows 2012 R2 server.  What we are trying to accomplish is very easy on Netware and we are having a difficult time replicating this on the new Windows server.

Basically on Netware if a user has access to a folder nestled deep inside several other folders, Netware automatically gives the user the necessary rights to browse through just the folders necessary to get to that folder while not allowing them to see any other folders or files that exist in folders along the way.  We are trying to accomplish this and it looks like ABE is the way, but it doesn't seem to be doing what we want. It's highly likely we are doing something wrong.

In the picture posted i'd like to give someone access to the Recovery Keys folder, allow them to browse to that folder, not see any other folders that exist under the Admin folder no see the TPM folder.  We are planning on mapping a drive letter directly to the fileshare share.  Is this possible and if so please assist us in figuring this out.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
We migrated a client from Novell to Windows 2012 Standard about a year ago.

That turned out to be a bit of a rat's nest since Novell allowed for folder traversal with contents hidden while AbE does not do same.

We ended up having to re-architect the folder structure:
Root share: Company with AbE
 + HR (HR and Admin Groups - Disinherit & remove Users)
 + Finance (Finance and Admin A/A)
 + Marketing (Marketing & Admin A/A)

And so on. It was about the best solution we had available to us. PowerShell helped a bit with the permission sets as there were a LOT of folders under the root.

EDIT: BTW, ForensiT's Profile Migration Wizard was _AWESOME_ for automating the migration of the user's local profiles into the newly established domain setup. It was 165 desktops.
DamonVanAuthor Commented:
That's what  i was afraid of.  I just need someone to confirm my suspicion.

Thanks for the answer.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now