Discussion Locked

Private Home folder quota problem

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi.

We're using 2003 R2 w/ File Server Resource Management (FSRM)

I've applied a hard quota of 2.0 gig to each private user drives.

The user permissions are not set to inherit. and the drives are stored on the root of a physical volume E

example \\server\E\username

I've defined their home folder location through Active directory and using %username% to give them full control over their folder.

The folders create fine and they can interact with their folder.

Here's my problem.

When they log in to their XP machine, they see the total space on their "User on 'server\users\' mapped Z:\ drive.

Does anyone know why Windows XP won't show their specified quota of 2.0 gigs and have it act like that? I saw this done once before at another company, but have lost my contact there to ask.

Any help would be appreciated.

7 replies

by Former member

On the mapped drive "z" go into the "quota" section then quota entries and then you would be able to select how many gb's or kb's each user has and can see. I hope this works for you. Please post back if you have anymore problems.

by legendzm

The Z:\ drive gets mapped through the Domain Users & groups, Right click a user, then go to profile and I enter the UNC to the home folder \\server\e\%username%
I was using the File System Resource Manager in R2 to create a parent quota system on the physical drive E on the server to all sub directories.

The quota works, they can't use more than the quota i've put on,
but when Z:\ is mapped to (from the profile section of their user profile)

they see the entire drive's free space.

Any help is appreciated

by legacyb4

I was beating my head against the wall for the same reason then came across a post summarizing:

Case 1: (quota on the root of a share)
Volume D:\ with 20 GB free space
D:\foo is shared as \\server\foo

There is a 100 MB hard quota on D:\foo

On the client, \\server\foo maps to O:\. Then the free space reported on O:\ will be 100 MB

Case 2: (quota on subfolder in a share)
Volume D:\ with 20 GB free space
D:\foo is shared as \\server\foo

There is a 100 MB hard quota on D:\foo\bar

On the client, \\server\foo\bar maps to O:\. Then the free space reported on O:\ will be 20 GB because SMB directs all free space queries to \\server\foo

Apparently, this has been fixed in Windows Vista (I've tested) but XP users are out of luck.

by legendzm

I still cannot get the mapped drive to display the correct amount of quota left for the user, instead the entire drive's physical limit is displayed

by jeffusa

The only thing I have figured out so far is that if the network drive connects to a folder on the root of the drive on the server it will display the correct quota info. However, if the folder is more than one folder down in the hierarchy liek most user shares are it will display the incorrect quota info.

This discussion is closed to new replies.