Setting size of Mapped drive

[cheeseslice]

could anyone throw a few suggestions my way.

I have written a script that allows the user to log onto a NAS and map a drive to their computer. When they run the script it checks to see if a folder on the NAS matches their logon name, if it doesn't it creates this and then maps drive letter K: to this folder.

The problem I have is that people are now abusing this and using more space than I can afford. I have got to the stage where the script will now get the size of all of the files in their mapped folder and check it against the set limit but I don't know what would be the best way to proceed. I have been trying now for 2 days to implement a file browser which would only allow the users to delete or move the files but I'm not having much success.

Can anyone think of an easier way to do this. Basically I don't want them to be able to do anything to the folder except move or delete files from it.

Is there an attribute that can be set on a folder for delete only? maybe that's wishful thinking.

Any thoughts would be much appreciated.

[PsaltyDS]

You need to implement storage quotas on your NAS or by by domain policy.

[cheeseslice]

there are no options to set quotas on the NAS unfortunatley. (i wish there were)

the only way i thought of getting around this was to keep the focus on the gui that i have created and make the user either delete or move the files there and then. i was hoping i just missed some easy option.

[james3mg]

Do you have access to NTFS permissions on the folder? If so, you can use the cacls command-line command to change their users' permissions to allow only "Traverse folder / execute file", "List folder/read data", "delete subfolders and files", and "delete" until they've freed up space, then run it again to restore "full control". That should do the trick, because even though they could still open up read-only versions of the files, they can't save anything to the folder then...making it useless to continue until they've freed up space. In fact, they may NEED to be able to open the files read-only so they make sure of what they are deleting.

Regarding quotas, that really is the best way to do it - have you enabled quotas before? You have to turn quotas on for a DRIVE on the server, not on a per-folder basis. Then you can set limits and exclude users (think "Administrator") as you wish. Just want to make sure you really can't enable quotas before you write an entire different method in a script . If you know what you're doing and quotas really aren't available, then just skip this last paragraph