Anyone have a a reason to believe this issue has gone away (and if so how?):
Why disk space is incorrectly reported on folders where File Server Resource Manager quotas are enabled
At a glance my numbers aren't working as described in the link (I'm in Case 2 land with XP clients).
It implies you need Vista/7..., it's more client sided limitation... I've seen people make reference to junction/reparses... but I glazed over and didn't have a clue what either were...
However, you can look at possibly using NTFS quota's AND/OR FSRM quota's... NTFS quota's do work and return the correct cap size (I think... I can't remember, I wanted to it ages ago but couldn't be bothered with the next step),...
But, data is capped against the owner of the file, so as long as xyz creates the file... it'll track it, if not, you're stuck - which is where my plan failed because I owned 400gb of data... and nobody else owned anything.
There are currently 1 users browsing this thread. (0 members and 1 guests)