I am thinking about breaking it up in to 2 time groups.

Group 1 is ran once every 10 min, but this scan will only check the users that are close to and or over the limit (only using the information that is supplied from the database, and not doing a full diruse scan).

Group 2 would run once every 2 hours and it would run doing a full diruse scan

Thinking about using a 3 strikes your out rule too. You will have to be over your limit for 3 scans in a row before write access is removed. This is where I would like to use email as a warning tool.

I would like to have some way of notifying the user that their user folder is over it's size limit, and i can only use their USERID to do this. If all my users were NT i would just do a "net send" message, but.... this is not the case.

Bryce