Hi i am resetting up our file server and i have 2 parations one for Windows and one for data. I want everyone at my work to have access to the files and folder, but i want to stop every one from deleting them. What permissions do i need to set on the root of the F drive so it propagates to all the subfolders and files so i never hear the pharse, my stuff is gone.
Thanks

You can't do it via rights.

Invest in a server undelete program which is the best way of handling "my stuff is gone" along with tested backups.

Imagine the power if you knew how to internet search

Wanderer, are you sure that's true?

I mean, you can set permissions for each folder or file therefore protecting it from other users.

Unless your point was that servers, like other computers, crash.

It usually takes more than three weeks to prepare a good impromptu speech.
- Mark Twain

seawatch1 writes:
"you can set permissions for each folder or file therefore protecting it from other users"

But sbertram states:
"I want everyone at my work to have access to the files and folder, but i want to stop every one from deleting them"

So seawatch1 how are you going to grant full permissions to work with the files yet take away the delete right so they can't delete them? Users would not be able to even have Word autodelete the temp file created everytime a Word doc is opened and closed without the delete right.

What sbertram wants can't be done via rights assignments alone.

Imagine the power if you knew how to internet search

Would they have to have full control?

Can't you just set the permissions to Read/Write without the ability to delete as it's a separate permission?

I'm asking, not arguing.

It usually takes more than three weeks to prepare a good impromptu speech.
- Mark Twain

"Users would not be able to even have Word autodelete the temp file created everytime a Word doc is opened and closed without the delete right"

seawatch1 create a folder. place a text file in it. Deny full control and only do list, read and write for everyone. Now edit the file and do a save as. What happens? Do a couple of file opens and save as's. What do you see? Now take it one step further. Open one of the saved files, edit it, and now save it as one of the already saved files. Saved didn't it? Now make a folder. Go into that folder and make another one. Can you delete it?

Removing all rights and only having list, read and write results in the following:

1. *.tmp files accumulate
2. if you do a file save as it asks do you want to overwrite. if you answer no you end up with the file name but a 0 byte file.
3. you can save over an existing file thereby overwriting the original with something else.
4. you can create nested folders but if you make a mistake you can't delete them

Now just imagine what this would be like with 10 people in one folder editing and saving files. Even if those 10 people only edited a single file every edit would result in a tmp file they can't delete. It is even worse if running a program which can write and delete 100's if not 1000's of temp files during its operations.

Hence the advice of an undelete program to address the phrase "my files are gone" along with good backups.

Imagine the power if you knew how to internet search

I see. Great explanation, wanderer.

Thanks.

I always learn something here.

Larry

It usually takes more than three weeks to prepare a good impromptu speech.
- Mark Twain

Great question. Always glad to help.

Imagine the power if you knew how to internet search

As a secure Windows user, I have a music profile that is set up exactly like this. No offense Wanderer, but NTFS permissions are perfectly sufficient. I have my music so it is readable, but not writeable or deletable. All it takes is a simple NTFS permissions set under a net of users on the domain. This is specifically what NTFS permissions were designed for, and I used that to lock my machine down to the ground, along with GPEDIT and safe zone configuration. Not to mention the settings that can be done in Registry and IPSec. Anyone managing a server should know this.