Disk Quota not working ... or is it?

[ihaveaproblem]

Server 2003R2 File Server.
Using FSRM to set quota on home drives
Have a template created with the quota size and set it as hard.
Made a new quota, linked it to the correct template and selected the 'Auto Apply template and create quotas on existing and new sub folders'
The quota seems to work because the user accounts cant save over the quota limit on their home drive.
The problem is this

1.PNG

The drive is still show the full size instead of the quota limit size. When i've set this up in the past it's always shown the quota size instead of the full hard disk size (e.g 350mb of 500mb)
Have I missed something?

Client machine is Win7 x86 Enterprise if makes any difference.

[DMcCoy]

Folder level quotas will only show the right sizes with an smb 2.0 server and client (Windows 2008 and Vista onwards). smb 1.0 does not have the necessary commands to check a folder for quota information.

[ihaveaproblem]

Folder level quotas will only show the right sizes with an smb 2.0 server and client (Windows 2008 and Vista onwards). smb 1.0 does not have the necessary commands to check a folder for quota information.

Baaaah that sucks!
Ok.. so I will rebuild the file server on Server 2008 R2 when I get chance =]
Thanks DMcCoy

[CyberNerd]

Baaaah that sucks!
Ok.. so I will rebuild the file server on Server 2008 R2 when I get chance =]

or a samba server. We put all our quota on linux/samba to overcome this limitation in 2003 (before 2008 server was released) - theres a lot of quota options as well as some nice features like network recycle bins, veto filetypes/sizes quota email, auto homedrive creation etc.

[Boredguy]

When our users check their network drives, it clearly shows their current space based on the drive quota and thats with Windows 7 Enterprise clients and the quota drives being on Windows 2003 R1 servers.

[3s-gtech]

2003 R1 doesn't have FSRM, so your quotas must be set elsewhere. It's with FSRM quotas on 2003 R2 (and Samba 1.0) that this problem applies, and with XP clients on SMB 1.0 or 2.0.

[salan]

At the risk of 'hi-jacking this thread'
I am having trouble setting quotas for pupils home drives. THe setup is as follows.
U:\ is there 'my docs' etc. i.e. there home dir.
This is ina folder sturcture on the server like this.
d:\home\07\07fredj
d:\home\08\08smithc
When I have tired to put quotas on, they go onthe home dir.
Its obviously me not getting my head around this but can some one help/point me to an article that goes through doing this please?
Alan

[ihaveaproblem]

At the risk of 'hi-jacking this thread'
I am having trouble setting quotas for pupils home drives. THe setup is as follows.
U:\ is there 'my docs' etc. i.e. there home dir.
This is ina folder sturcture on the server like this.
d:\home\07\07fredj
d:\home\08\08smithc
When I have tired to put quotas on, they go onthe home dir.
Its obviously me not getting my head around this but can some one help/point me to an article that goes through doing this please?
Alan

Hi Alan,

Did you set the quota path on D:\home ?
Set the quota on the year folders instead, so D:\home\07
You will have to make a couple of quotas though to point it at each year folder.

[Naughty_Nigel]

Disk quotas work best on clean drives. When you set disk quotas on existing drives the OS doesn't automatically know who the files belong to, so if you allow 'John Smith' 500 MB, he will get 500 MB plus the files he already has on the drive!

It is possible to set ownership of files manually, but that is a real faff.

NN

[3s-gtech]

^^It can be done using chown.exe and a little script - this sets the folder owner as the folder name. I use this to reset 900 odd owners for FSRM automatically.

rem sets permission on all files according to home directory name, place this and chown.exe into the \homefolder folder then run it.

for /D %%i in (*) do (
chown -r %%i "%%i\*.*"
)

[Naughty_Nigel]

^^It can be done using chown.exe and a little script - this sets the folder owner as the folder name. I use this to reset 900 odd owners for FSRM automatically.

rem sets permission on all files according to home directory name, place this and chown.exe into the \homefolder folder then run it.

for /D %%i in (*) do (
chown -r %%i "%%i\*.*"
)

That is useful advice, thank you.

From what you are saying, folders must be given the same name as their owner if this script is to work, and owners can only save files in their own folders. This should work well enough in an educational environment, but is not so easy in a workplace.

SB

[3s-gtech]

Yeah - I have the username as the foldername here (created en mass when the users are created and set via AD) so it easily associates the two. Owners can only save files in their own folders due to NTFS permissions - they cannot browse for other folders or enter them anyway, so the ownership doesn't make a difference there. This could be applied to the workplace with a change of policy - for instance, our staff have the same settings applied to their home folders.