No, it doesn't matter who puts the files there nor who owns them--you can't even go over the allotted amount with an administrator account-you would have to bump up the storage amount. Old-style volume level quotas do rely on ownership, and with third party software you would have to look-it varies from vendor to vendor.
Something else, in terms of wording. We like to call our quotas a "storage allotment" or "Allowed Space" when talking to end users. Seems a little thing, but people like to hear that they are allowed and given space rather than restricted from it-goes over a lot better =) One other caveat I would just mention is that if you are already using File-level AV software and VSS snapshots (via MS tools), and you are NOT already running on an x64 WS03 Server system, watch your kernel memory usage with adding quota. Over the many years of using first third-party and then Microsoft's FSRM quota, we have found it is a lot to load into kernel memory and you can easily run out of resources when serving up a lot of file shares. If you start to have trouble, start with following this: http://support.microsoft.com/kb/312362 If changing the above settings is not enough over time, you will have to think about going x64. We had a server that last year had major kernel memory issues due to this and after much research and monitoring, we decided to reinstall over the summer as x64. Exact same hardware and this year we are not having these problems. -Bonnie From: Ziots, Edward [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 5:31 AM To: NT System Admin Issues Subject: RE: Question Disk Usage Policiies Lookign for comments Folder level quota in FSRM R2 is based on Ownership correct? I am reading up on the drafting of the policy right now, and going to work out the how particulars as soon as I get some budget approval. Z Edward E. Ziots Network Engineer Lifespan Organization Email: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> Phone: 401-639-3505 MCSE, MCP+I, ME, CCA, Security +, Network + ________________________________ From: Miller Bonnie L. [mailto:[EMAIL PROTECTED] Sent: Saturday, December 06, 2008 5:37 PM To: NT System Admin Issues Subject: RE: Question Disk Usage Policiies Lookign for comments A little late here, but yes (we use here for kids, with quite the list), they can rename an extension, but then they generally can't use it while it's sitting on the file server unless they know how to re-associate file types (and have access to) or get it to open another way. In other words, if they want to actively use it they have to copy it off to somewhere else (c drive, thumbdrive, etc). This gets annoying after a while. We also use FSRM in R2 for folder-level quotas. Also, make sure to figure out how you will document the quotas and the exceptions. At times you might find yourself needing to restore/migrate the settings, and rebuilding it from memory is not good =) From: Ziots, Edward [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 12:16 PM To: NT System Admin Issues Subject: RE: Question Disk Usage Policiies Lookign for comments Simplistic approach, I like, but the deny all and allow only what needed approach in a hospital setting probably isn't going to work the best. I know what the big space abusers are, I could use file-screening in Win2k3 to block certain types, but its easy to get around that with just renaming the extension and I am sure some savvy user is going to do it and bypass the controls. Z Edward E. Ziots Network Engineer Lifespan Organization Email: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> Phone: 401-639-3505 MCSE, MCP+I, ME, CCA, Security +, Network + ________________________________ From: Kevin Lundy [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 1:53 PM To: NT System Admin Issues Subject: Re: Question Disk Usage Policiies Lookign for comments ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
