RALPHQC
asked on
stop user from deleting files on a shared drive
I am missing two directories entirly on my server. I would like to setup my users so they cannot delete anything. I tried to audit file access but i dont get to see which file they deleted only that a file was deleted. I think the best way is to not allow anyone to delets . Its a database server, file server and app server. thanks
puterhead
remove the modify or full control permissions on the folders by right clicking on the folder and going to the security tab. Allow only adimistrators modify or full control.
Yeah deleting access just comes under modifying. And if you want your users to use the files properly, they need modify.
So I'm a it lost. Are you trying to: (a) find the culprit, (b) find the deleted file/s, or (c) prevent the culprit from deleting files. Well if (a), it sounds like you alreay have the culprit. If (c), then you have to deny that user modify access, or keep a backup and restore when desired. If (b), then you really need a copy of the files to compare to every day.
The way that I know of (there's probably many), is to use a program called robocopy. Its now part of the MS Resource Kit, but you can download separately here http://www.devhood.com/tools/tool_details.aspx?tool_id=321
It'll take you some time to learn and practise the switches. You'd want to setup 2 scripts: 1 that mirrors all the folders/folders to somewhere else (a full replica) and then 1 that does a simulated copy, only logging the files that differ. You culd run the 2nd script to check what has changed. Then when you're happy, run the 1st one to copy the updated files to your backup.
It's a lot of work, but I think any solution will be that involves you constantly monitoring which files are getting deleted and trying to replace them. Better to find the source (the user) and cutoff the problem (modify access) for that user.
So I'm a it lost. Are you trying to: (a) find the culprit, (b) find the deleted file/s, or (c) prevent the culprit from deleting files. Well if (a), it sounds like you alreay have the culprit. If (c), then you have to deny that user modify access, or keep a backup and restore when desired. If (b), then you really need a copy of the files to compare to every day.
The way that I know of (there's probably many), is to use a program called robocopy. Its now part of the MS Resource Kit, but you can download separately here http://www.devhood.com/tools/tool_details.aspx?tool_id=321
It'll take you some time to learn and practise the switches. You'd want to setup 2 scripts: 1 that mirrors all the folders/folders to somewhere else (a full replica) and then 1 that does a simulated copy, only logging the files that differ. You culd run the 2nd script to check what has changed. Then when you're happy, run the 1st one to copy the updated files to your backup.
It's a lot of work, but I think any solution will be that involves you constantly monitoring which files are getting deleted and trying to replace them. Better to find the source (the user) and cutoff the problem (modify access) for that user.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Another way is to use Shadow Copy. Have it to run like 3 times a day for the directories you want to protect. Then its very easy to restore a specific version of any file. It's built-in and free.
http://www.youtube.com/watch?v=EcJs5JKexZ0
http://www.youtube.com/watch?v=EcJs5JKexZ0
ASKER
if a user creates a file he can still delete it. I could not stop people from deleting their own files.
> if a user creates a file he can still delete it.
if the user has no Full Control access to the folder, by removing the Delete File permission, the user can't delete the file after creating it.
if the user has no Full Control access to the folder, by removing the Delete File permission, the user can't delete the file after creating it.