The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.
Solved
NTFS security - Folder Security
Posted on 2004-09-08
Hi!
I don't want the users in the network to be able to create, delete og remove folders at root level at our server.
We have 6 folders at root level which "domain users" are NOT supposed to create, move or delete files or folders at this level. (Wich they often do by mistake)
All users are members of "domain users".
I have tried to give the users restricted acces to the folders, but it has not succeded.
Eighter they gets denied, or they still get full access.
Sharing permissions tab shows "Domain Users" "Full Control" , "Change" , " Read".
Security tab shows "Authenticated Users" and "Domain Users" - Modify - Read & Execute - List Folder Contents - Read - Write.
Advanced Settings: Access Control Settings: Deny "Users" , Deny "Authenticated Users" - Change permissions , take ownership.
I have tried to deny "create folders / append data , create files / write data. I applied the settings by using " Apply these permissions to objects and/or containers within this container only". I am not getting the result I'm looking for.
Usually users don't get enough user rights, and I have to reset to "full access" so that everyone can start working again.
As mentioned above, I want to be able to deny users to do anything about the folders at root level. (6 folders which are shared). All users have mapped this folders by a loggon script. The users are not supposed to create files in theese 6 folders or above eighter.
My settings like they are right now is working in a way taht everyone gets access to the files. This is a temporary solution. Looking for a good solution. We have only 33 employees.
Anyone with long experience within this field?
TrondL
I don't want the users in the network to be able to create, delete og remove folders at root level at our server.
We have 6 folders at root level which "domain users" are NOT supposed to create, move or delete files or folders at this level. (Wich they often do by mistake)
All users are members of "domain users".
I have tried to give the users restricted acces to the folders, but it has not succeded.
Eighter they gets denied, or they still get full access.
Sharing permissions tab shows "Domain Users" "Full Control" , "Change" , " Read".
Security tab shows "Authenticated Users" and "Domain Users" - Modify - Read & Execute - List Folder Contents - Read - Write.
Advanced Settings: Access Control Settings: Deny "Users" , Deny "Authenticated Users" - Change permissions , take ownership.
I have tried to deny "create folders / append data , create files / write data. I applied the settings by using " Apply these permissions to objects and/or containers within this container only". I am not getting the result I'm looking for.
Usually users don't get enough user rights, and I have to reset to "full access" so that everyone can start working again.
As mentioned above, I want to be able to deny users to do anything about the folders at root level. (6 folders which are shared). All users have mapped this folders by a loggon script. The users are not supposed to create files in theese 6 folders or above eighter.
My settings like they are right now is working in a way taht everyone gets access to the files. This is a temporary solution. Looking for a good solution. We have only 33 employees.
Anyone with long experience within this field?
TrondL
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
5
2
11 Comments
just give read access to your "authenticated users" at root level (folder security). that will do the trick.
btw... you will need to break rights inheritance in subfolders, because permission will be propagated..
And if your users are members of other group, like domain users, and this group have access, they will get access to it anyways. I would give read access to "domain users", and full access to administrators. that'S it, nothing else.
Active 3 days ago
Make the Root Folders "read only"
then inside the folders change the permissions of the folders/files to the security that you have.
make sure that the child folders dont inherit permissions from the parent..
example:
root1: <- read only
- child1: <-- full control
- child2: <-- full control
root2: <- read only
- child1: <-- full control
- child2: <-- full control
basically the design is make sure the door to the room is secure, but the information behind the door is wide open once the people are inside.
then inside the folders change the permissions of the folders/files to the security that you have.
make sure that the child folders dont inherit permissions from the parent..
example:
root1: <- read only
- child1: <-- full control
- child2: <-- full control
root2: <- read only
- child1: <-- full control
- child2: <-- full control
basically the design is make sure the door to the room is secure, but the information behind the door is wide open once the people are inside.
Active 3 days ago
sorry bout that man.. i read the question, and just started typeing an answer in.. didn't even dawn on me to look at what had been written.
I am not sure about your config.
You say "I want to be able to deny users to do anything about the folders at root level. (6 folders which are shared). All users have mapped this folders by a loggon script."
Which folders are actually shared on your server?
Is there one shared folder that contains the 6 folders?
Or are there 6 different shared folders?
If all 6 folders are shared individually, then the only way they could get to the root (i.e. above those share points) is if there is another share defined for the root itself.
What are your client computers? This can make a difference.
How do you map the drives? Can you post the net use commands from the login scripts?
You say "I want to be able to deny users to do anything about the folders at root level. (6 folders which are shared). All users have mapped this folders by a loggon script."
Which folders are actually shared on your server?
Is there one shared folder that contains the 6 folders?
Or are there 6 different shared folders?
If all 6 folders are shared individually, then the only way they could get to the root (i.e. above those share points) is if there is another share defined for the root itself.
What are your client computers? This can make a difference.
How do you map the drives? Can you post the net use commands from the login scripts?
Featured Post
We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
During and after that shift to cloud, one area that still poses a struggle for many organizations is what to do with their department file shares.
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually.
After setting up a router, find the network security…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Suggested Courses
Course of the Month5 days, 22 hours left to enroll
688 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.