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/> ~
