Windows 2000 Disk Quotas for Domain Users

In Microsoft Windows 2000, disk quota enforcement allows administrators to manage and restrict storage consumption on NTFS volumes shared across domain networks. Rather than monitoring network shares or folders individually, Windows 2000 tracks disk usage per user and per volume using the underlying NTFS file system. This article explains how the operating system identifies domain users, calculates their storage consumption, enforces usage limits, and handles capacity restrictions when multiple users share the same storage volume.

Per-Volume NTFS Architecture

Disk quotas in Windows 2000 are built directly into NTFS 5.0 and operate strictly on a per-volume basis. They do not monitor individual network shares, folders, or directory trees. If an administrator creates multiple network shares on a single volume, a user's combined usage across all of those shares counts toward one single quota allocation for that volume. Conversely, if storage spans multiple volumes, an administrator must configure quotas on each volume independently, as quotas cannot span across volumes.

Ownership-Based Tracking Using SIDs

Windows 2000 calculates quota consumption based solely on file ownership. When a domain user creates, moves, or saves a file to a network share, the operating system assigns that user's domain Security Identifier (SID) as the file owner.

Key attributes of this tracking model include:

  • Uncompressed File Size: Windows 2000 measures disk quota usage by the uncompressed, logical size of files. Utilizing NTFS file compression does not reduce the quota amount charged to the user.
  • Non-Transferable Usage: Modifying an existing file owned by another user does not shift the quota burden; the file continues to count toward the original owner's quota until ownership is explicitly changed.
  • Domain Accounts: Because ownership relies on standard SIDs, domain accounts are recognized and tracked transparently across the domain environment on any Windows 2000 member server hosting the shared volume.

Enforcement Policies and Thresholds

Administrators configure two primary thresholds for users on a volume: the Quota Warning Level and the Quota Limit.

  • Warning Level: When a domain user's total owned files exceed this value, Windows 2000 can record an event in the server's System event log. This alerts administrators to heavy storage usage without interrupting the user's workflow.
  • Quota Limit: This serves as the maximum allowable storage for that user on the target volume.

Actual enforcement depends on whether the administrator enables the "Deny disk space to users exceeding quota limit" setting:

  • Soft Enforcement (Denial Disabled): The user can continue writing files past their limit, but Windows 2000 logs a warning event in the event log.
  • Hard Enforcement (Denial Enabled): Once the user reaches the assigned limit, the operating system blocks further write operations. When an application or user attempts to allocate more space, Windows 2000 returns an "Out of Disk Space" error (ERROR_DISK_FULL), exactly as if the physical hard drive were full.

Default Limits and Custom User Exceptions

By default, volume-wide quota properties apply identically to all domain users accessing the shared storage. However, Windows 2000 allows administrators to create custom quota entries for specific domain users or groups.

Using the Quota Entries window in the volume properties, administrators can grant elevated storage limits or exempt particular users (such as backup operators or department heads) from quotas entirely, while maintaining strict default limits for standard domain users.