Question Locked

Best way to control user access to files and folders.

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

Ongoing debate with a collegue. He says use Group Policy to control user access to files and folder e.g dumping users into an OU and set file/folder permissions that way e.g. user rights assignments.

I say use the global groups/domain local groups model and set permissions for folders and or files per group and dump users into groups you want to have permission.

17 replies

by tintoman

would not pass the Microsoft server administration exam with his solution although it obviously works for him.
You on the other hand are suggesting exactly what Microsoft teach.
Personally I think your answer is a better solution in the long term when it comes to adding new users

by cg it

to control access to files and folders.

He thinks that changing user rights assignments via group policy is the best way to control file/folder permissions. So he wants to configure a group policy with settings in the user rights assignments. He figures that if he changes user rights he can effectively control user access to shared files/folders.

were I want to create file/folder permissions which apply to groups and dump users we want to have access to a file/folder into that group.

by wancona

I personally use the same method as your collegue. It may not be the "Microsoft" way, but it works for me.

by cg it

via rights instead of permissions?

by wancona

I had read this some time ago, and it made sense to me...

Quoted from Microsoft

User Rights Assignment Settings
In conjunction with many of the privileged groups in Windows XP Professional, a number of user rights may be assigned to certain users or groups that typical users do not have.

To set the value of a user right to No One, enable the setting but do not add any users or groups to it. To set the value of a user right to Not Defined, do not enable the setting.

You can configure the user rights assignment settings in Windows XP at the following location in the Group Policy Object Editor:

Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment

by bart777

You are right.
The best way is always via groups and folder permissions. GPOs are nice but this isn't what they were designed for.

Normally I setup the share permissions so that Domain users have full control and set the actual security via NTFS. Since shares only have 3 levels of security and NTFS can be highly customized it's a much better choice.

Best of luck with the debate. If he decides to take it further tell him to go and grab any cert book for 2003 and he'll see how wrong he is.

by cg it

I understand what he wants to do by using rights and configuring it via GP but then there are permissions as well.

We have a shared folder that we wish to restrict some users but not all users from accessing and further restrict what some can do read/modify while some only read.

I guess my way is mor of an administrative effort [requires lots of documentation] and his way is easier [just a GPO] but I can't see how his way is as grandular as using NTFS permissions.

The other thing is delegating authority. I'm afraid that his way will open up a can of worms when we delegate authority for creating user accounts, reset passwords etc.

by bart777

If you start having problems with GPOs due to a change or addition to a policy you can leave yourself open for problems.

Once NTFS is set and you have the subfolders set the way you want in the master share you are done.

Adding and deleting users from groups is far easier than trying to figure out why 2 policies that have some form of overlap are causing issues.

by kjell_andorsen

I definitly feel your way is far superior as it allows for a far greater level of flexibility and granular control.

His way might work if everyone in an OU should have the exact same rights, but in most organizations this will lead to a very complex and unwieldly OU structure very fast. Also users can only be in one OU at a time which makes things unescessarily hard to manage.

Using NTFS security groups allows far more control and flexibility and has few if any drawbacks to managing by OU. I mean, I love GPO, but the idea of managing all file and folder access to it instead of security groups is the kind of stuff nightmares are made of.

by kjell_andorsen

Yeah, but this is not intended to be for folder and file access, this is for special rights such as being able to add a printer, or performing backups/restores etc.

I have frankly never heard of anyone using GPO as the primary means of controlling access to files and folders. It's definitly not considered best practice.

by cg it

and we have numerous shares in which to control access to. Some users require just read, some read/modify. Other users we want to deny access.

Some shared folders are really DB folders [Acess DB] which are required for applications to run. There are users who shouldn't be able to access that shared folder by browsing the network [when they don't have the application installed on their desktop]. But I found out that with his GP, they can because their in the OU which has user rights assignments configured.

Which started this whole debate.

by cg it

but I'll give everyone who responds a thumbs up.

by Former member

Seems like your AD replication would get fairly bogged down trying to manage your OU structure over time. (We have several thousand folders with different controls required. The 'MS' way allows you to create groups with names the clearly identifying the resource and level of permission you are enabling (DL), and an intermediary group with a name that defines the role (Global/Universal) That way, permissions are assigned to Roles, and and users are added to appropriate roles. A change in a Role definition? No problem, just add/remove the appropriate Domain-Local groups. A user changes Role, or receives new responsibilities? Again, no problem, just add/remove the appropriate global groups. A little more complex to set up initially? Maybe. But I think much easier to maintain and support ongoing.

by cmiller5400

Don't know why you would use GPO to do this, when they give you NTFS permissions; they give you better control. Plus if a user needs to be members of several "groups", that could get very messy, very quickly if using GPO...

Just my 2 cents...

by cg it

the plan my collegue came up with was to create 8 OUs called Access Control List, toss users into them, then assign rights. His plan doesn't really say what rights he's using to control who can access what.

He's also got shared folder permission on one folder, as an example, with the everyone group with full control and then assigned individual user accounts, individual permissions for that share. My gripe if the individual user accounts and individual permissions per user account. To me that's more of a mess to figure out permission problems for users than using groups.

by Former member

It is fairly typical practice to set everyone/full (or authenticated/full) for the share permissions. The Filesystem permissions will take precedence over the share permissions. So rather then dealing with two sets of permissions, opening the share permissions and then restricting permissions on the files and folders is fairly common (If I am understanding you correctly).
The benefit of groups, vs. adding users directly- Much easier to later on see who has access to what. If you assign user directly to shares, how do you later identify/recall what the user has been granted access to? (Sure, there a scripts and 3rd party tools to accomplish this, but if you're using groups, it is all there and easily accessible in ADU&G).

This discussion is closed to new replies.