File Permissions to modify but not delete files

We are trying to get as close as we can to permissions that allow users to modify files, create new files, but not delete any files within a shared network drive in Windows Server 2008 environment. I have done a bit of research already, but so far it hasn't yielded much. Any help here would be appreciated. Thanks!
Leverage IT ConsultingAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
I think that is because if you can modify a file, you can (inadvertently or otherwise) destroy the contents.

Have a good backup system and deleted files are very easy to recover. You should have backups anyway.
Will SzymkowskiSenior Solution ArchitectCommented:
This is quite easy to do. On the directory you want to modify all you need to do is the following...
- Right click, on the directory, select properties
- Select Security Tab, click the Advanced Button
- Click the Change Permissions button
- Click the Add button
- Add the user or group you want to allow permission
- From there you can select the permissions that you want to apply to the user

Just make sure that you do not select Delete as one of the permissions.

Thats it.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Bryant SchaperCommented:
you may also run into application issues.  In the past for example, Excel seemed to not work with this, everytime you save the file it seems to delete and create the file, maybe moving the temp file or something.  But the steps Wil has is correct to set the permissions.
andreasSystem AdminCommented:
But this will only "protect" you from the accidential delete on the file share. If a user wants to remove content he just opens up the app load the file, press ctrl+a click press delete and save the file.
Then you have a nice file with just a header and no contents, or if asci or other headerless files, just a file with 0 bytes lenght.

Its also not a protection against malware, in worst case malware will open files to manipulate them and not create a modified copy and delete the original. (e.g. malicious encryption)

So what are you want to achive with this setup? Maybe there are better ways to achive your goals.

Backups and snapshots as already suggested is a good thing too to prevent files from destruction, and they also cover overwrites...

Or setup an incomming directory, where only writing is allowed, from there distribute the files to sharing directories and set them read only.
If names are duplicate in incomming your copy cript needs to change names a little bit.
This way all users can write new files to a place where all with permissions on that share can read them without any chance to destroy anything.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.