Informing users they are over their quota? (2003 R2)

[sidewinder]

Just been setting up quotas for the students on R2 using the FSRM.

All works well, except I cant think of a good way to inform them to delete some files if they go over the threshold.

 

Obviously the message about the disk being full and them needing to delete some files when you try and save anything else gives a good clue but Ive got the feeling a lot of students will see that as 'The network isnt letting me save' rather than 'I need to delete some files' and will lead to loads of complaints

 

The email facility built into FSRM is no good as we dont have an Exchange server and I doubt they would noticed the emails anyway

 

What I need is a little pop up or something saying they have exeeded the quota by xxmb and could they delete some files or see the IT Team.

 

I seem to remember with the NTFS quotas there was a way to have a baloon pop up to tell users they had exceeded the quota but I assume that doesnt apply to these new folder quotas?

[ChrisH]

Theres discussion of some scripts here

[BJG]

The link doesn't seem to work anymore...has anyone got a good solution to this...?

[BJG]

Thanks - I'm doing that, but I wanted to customise the message.

 

For future reference, this guy seems to have nailed it.

 

Disk Quota Notifications (Using Script) Not Working : Microsoft, Windows Server 2003, 2003, Storage Server

 

* * * * *

 

I used a .vbs script to run a net send command. Here were the commands I used in FSRM for the template I was setting up:

 

Run this command or script:

 

C:\Windows\System32\cscript.exe

 

Command arguments (note that [source Io Owner] is very important because the vbscript uses that to find the current user and send them a message):

 

//nologo "FULL PATH TO YOUR SCRIPT" [source Io Owner] [Quota Limit MB] [Whatever other args you want from FSRM]

 

Working directory:

 

Same as FULL PATH TO YOUR SCRIPT, minus the script name and last backslash

 

Run the command as:

 

LocalService

 

Here are the contents are my .vbs script:

 

'*******************************

 

'Turn on error checking

On Error Resume Next

 

'Declare variables

Dim objShell

Dim strUser

Dim strLimitMB

Dim intSlashPos

 

'Get arguments that were passed to the script through File System Resource Manager.

'You can modify this based on how many arguments you want to give the script in the

'"Command Arguments" field

strUser = WScript.Arguments.Item(0)

strLimitMB = WScript.Arguments.Item(1)

 

'Remove the "DOMAIN\" portion from the user name

intSlashPos = Instr (1, strUser, "\", vbTextCompare)

strUser = Mid (strUser, intSlashPos + 1, Len(strUser) - intSlashPos)

 

'Create the object

Set objShell = Wscript.CreateObject("WScript.Shell")

 

'Create the message to send - this relies on arguments that were passed

'from File System Resource Manager

strMessage = "Some message here. For example, your folder has reached the limit of " & _

strLimitMB & " MB."

 

'Send the message to the user

objShell.Run "net send " & [strUser] & " " & [strMessage], True

 

WScript.Quit

 

******************

 

I hope this helps others, cause I know how frustrating this is.

[jamesb]

Would WScript.Echo be a better choice than net send? That way net send can be disabled.

[BJG]

Can you generate a remote popup for a given user that way...?

[jack0w]

Does anyone know how this could be accomplished without the use of NET SEND?