In Windows 2000, Microsoft introduced disk quota policies, with which you can limit the amount of disk space that users consume on NTFS volumes. Disk quota policies also determine how the system responds when a user exceeds his or her quota limit or reaches a predefined warning level.
When you put disk quotas in place, you decide how the system will respond when users attempt to consume more disk space than you've permitted. If a greedy user creates a file that would exceed his or her allotted disk space, the user typically receives an Insufficient disk space error. The system forbids the user to write additional data to the volume without first deleting other files. Disk quotas are based on file ownership and, as such, are independent from the physical location of files on the volume. In other words, if a user simply moves files from one folder to another on the same volume, the overall space usage doesn't change.
Upon reaching his or her quota limit, the user can only delete files or physically move files to another volume that's under the control of another user. From the viewpoint of the quota system, compressing (or decompressing) files doesn't affect the amount of disk space consumed and subsequently doesn't affect the user's space allowance. Disk quotas are based on uncompressed file sizes. . . .
Register
