Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Read and write to a folder but not move it

Posted on 2010-11-08
2
Medium Priority
?
506 Views
Last Modified: 2012-05-10
We have a Server 2008 R2 file server used by everyone in the organization.  All share folders are using NTFS and group permissions, along with access based enumeration to govern folder access.  I have the groups set up with "Modify" rights to each departments folders.  We have a few departments who have bad habits of moving large folders and then losing them or forgetting where they are, etc...(typical user stuff).  At any rate, this may sound like a dumb question and I hope its not, but what specific permission set would be needed to allow read and write, but not move?  Should I turn off modify and just check read and write?  Do I need to go to advanced settings and create a custom permission set?
0
Comment
Question by:patriots
[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
2 Comments
 
LVL 15

Expert Comment

by:JBond2010
ID: 34087781
Read this link and this will provide you with all the information you need for Share and Ntfs permissions.

http://www.google.ie/search?hl=en&source=hp&q=windows+ntfs+permissions&aq=f&aqi=g2&aql=&oq=&gs_rfai=
0
 
LVL 42

Accepted Solution

by:
Adam Brown earned 1000 total points
ID: 34087956
With the basic NTFS permissions screen, there isn't a way to fix the problem you're dealing with. You have to use the Advanced permissions screen to do some more fine grained permissions modifications. http://articles.techrepublic.com.com/5100-10878_11-6084446.html has some more specific definitions of what each permission level does, and you'll likely need to do some testing and experimentation to get it working properly. Removing the Create Folders permission will likely help, but you may also want to limit the ability of users to Delete objects specifically. The average user probably shouldn't have the right to delete files in your shares, and that should be limited to Department heads or other administrative staff as determined by your company policy (if you don't have a company policy on who is allowed to delete files, consider writing one up :D). At any rate, pulling the delete permission from users will result in users being blocked from performing a Move operation, because a move implies a delete.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the absence of a fully-fledged GPO Management product like AGPM, the script in this article will provide you with a simple way to watch the domain (or a select OU) for GPOs changes and automatically take backups when policies are added, removed o…
Active Directory can easily get cluttered with unused service, user and computer accounts. In this article, I will show you the way I like to implement ADCleanup..
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Suggested Courses

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.

Join & Ask a Question