Question Locked

Users Browsing Home Directories in 2003 R2

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've been looking for a "real" solution for a while, and tested out several different flavors (see my links at the bottom). I am unable to set up home directories on the server so that users are unable to view other users files.

I am a part time IT person at a school, so I cannot have students able to look at other students files - it's a huge problem. Yes, I have UNC blocked in GP, but they can still create a shortcut on the desktop to go to it.

Also, teachers can not be snooping in other teachers directories due to student confidentiality laws. So I really don't even want them to see the files themselves.

What I need to do: block userA from seeing userB files on \\server\user$\

How I have it set up now:

Share Permissions:
Domain Admins: Full
Domain Users: Full

Security Permissions:
Domain Admins: Full
Domain Users: This folder only: List folder/Read Data
Creator Owner: Full

When I test this, the home directories are created properly via AD, but once I get a file up under test1 and test2, I can UNC to their directories & see, edit, or delete the files without an access denied.

Does anyone have suggestions for me?

Things I looked at to get here:
https://www.techrepublic.com.com/5208-1035-0.html?forumID=101&threadID=282032&messageID=2668752
http://www.computing.net/answers/windows-nt/creator-owner/18773.html
https://www.techrepublic.com.com/5208-11184-0.html?forumID=55&threadID=190883

13 replies

by kenone

Turn off inheritance <-Most Important
It doesn't really matter whether you use "Domain Users", "Everyone", or "Authenticated Users" it all depends on how you want to do it and how your domain is set up.
Step 2 on the main folder (users$) you need to restrict "users" to read/list only, then on each individual folder you would allow only that user, and administrator of course, full access. If you don't share the individual folders other users won't even be able to see them.
That's one way.

by churdoo

Did you turn off inheritance in the NTFS permissions of the Users folder? User Folder properties / Security / Advanced / uncheck "inherit from parent ..." / hit Copy / then remove all extraneous permissions.

Verify the permissions of the Users home folders to see what's being put there. When created, ADUC only adds the individual user to the NTFS permissions, but inherited permissions apply, so double check the NTFS permissions of a user folder to see what's being inherited.
--C

by cassiusaugusta

I did not break inheritance originally on the user folders, as I'd hope to continue to keep it that way. Also, I'm building the NTFS permissions directly from the share with/ drive so I can use quota management on the user folders.

Here's the inheritance vs. the server NTFS permissions:

test user folder:
Domain Admins: Full
Test1: Full (via AD - correct)
Creator Owner: (Advanced) Full

Share permissions:
Domain Admins: Full
Creator Owner: (Advanced) Full
Domain Users: (Advanced) This folder only: List folder / read data

And just to make sure, I checked out the AD groups, and the two test users are not in any group with more rights.

by kenone

Unless there is a good reason to, don't

by cassiusaugusta

I'm not sharing each user's home folder.

I've created a partition on the server, so that I can enable soft quota management. That partition is then shared, so that the folders created will be tracked for quotas.

I then have AD assign them their home folders, via connecting U: to the path that I tell it. I have GP map their my documents to the server.

I do this because it's very useful, I have a large number of teachers, and even larger number of students, and not everyone logs in on the same computer each time. And I'm pretty sure this is standard practice for any organization larger than a dozen people.

by cassiusaugusta

Ok, owner is set as the local server admin. When I remove the server admin from the share NTFS permissions, it doesn't allow the test users to browse the share, but if I know a person's login, I can UNC right to the folder & check it out.

But even with the server admin not on the NTFS permissions, it's still setting it to the owner. Is there a way that I can get around that automatically?

So, with server admin on the share, I have checked out the effective permissions (which I've never really looked at before.)

Domain users: Nothing
Domain Admins: Full
Administrator(network): Full
Creator Owner: Nothing
Everyone: Nothing

[And thanks for your help in my search for perfection!]

by churdoo

The Effective permissions look as I would expect them to, now also query the Effective permissions of user TEST1 on TEST2's home directory and vice versa.

So are you saying that if you login to a workstation as user TEST1, you can UNC to \\servername\users$\TEST2 and can browse TEST2's home directory???

by cassiusaugusta

Yes, the settings are the same for both folders viewed from the other test profile.

And if I remove the local server administrator from the root, logged in under the test accounts, I cannot unc to \\servername\users$\

On the other hand, if I know the username, I can UNC to their home folder, \\servername\users$\test2 logged in as test1.

So - if I can't find a solution, this might be as close as I can get to locking it down. It's still a vulnerability. Students are locked out completely from accessing teacher information on the share permissions.

But it would be nice if they weren't little twerps and created shortcuts out to the student directory. I've at least gotten the most tech-savvy on my side and they're helping me with issues.

by cassiusaugusta

Ok, so here's what works:

*Remove Local server admin from the NTFS permissions
*Create folders via AD
*Go to folders & remove inheritance
*Remove Local server admin from the NTFS permissions

So questions:
Why do I have to go back & touch the folders? I want it to be automagical :-D
Why is it inheriting the local admin when it's not in the parent folder?

Thanks for your help with this!

by churdoo

To answer your questions, I think because you stated that the Local Server Administrator is the owner of the parent users folder. This ownership is inherited and therefore NTFS permissions for the owner when the ADUC creates the individual user home folder.

If you change the Owner of the Users parent folder to DOMAIN ADMINS or an appropriate domain level object instead of a local object, and replicate the owner change to child objects, I think that will solve your problem and make it so you don't have to touch new home folders.

by cassiusaugusta

Theoretically, that does make sense. Except, in practice, even with owner set correctly on the parent folder, I'm still having the server admin pop up on the security permissions.

And I'm having the owner change back to the server admin. And I can't remove it unless I break inheritance.

With the teaching staff, that's not that big of a deal, but with some odd 1000 kids, that may a bit bigger headache down the road.

I tried removing Creator Owner permissions on the parent folder, in case that was turning out to give the server administrator the permissions, but the server admin still came back up on security permissions and as owner.

Thanks for your help with this :-D

This discussion is closed to new replies.