Disk Quota in windows

Disk quotas were introduced in Windows 2000, and are applied to specific users and limit the amount of disk space that user can use on a particular volume.
Windows 2000 disk quotas track and control disk storage usage on a per-user, per-volume basis. Windows 2000 tracks disk quotas for each volume, even if the volumes are on the same hard disk.

Directory quotas are applied to all users and limit the amount of disk space that users can use in a particular folder and its subfolders. Directory quotas were introduced in Windows Server 2003 R2 with the new File Server Resource Manager.

Note : You need NTFS volume for setting Quotas

How to set disk quota in 2000
—————————–
Mycomputer > select disk volume and right click > Properties > Quota
check the box Enable quta management
Limit disk space to :Configure the amount of disk space that users can use and
Set warning level to:Amount of disk space that a user can fill before Windows 2000 logs an event
Also Deny Disk Space To Users Exceeding Quota Limit check box

Setting Quotas for Per-User

Right click a drive letter > properties > Quota tab > Quota Entries > select user

Import and Export Quotas

Right click a drive letter > properties > Quota tab > Quota Entries > select Quota from top left > select the quota > import/export

Additional Quota options
————————
Log Event When a User Exceeds the Quota Limit – If quotas are enabled, an event is written to the system log on the local computer whenever users exceed their quota limit. Administrators can view these events in Event Viewer, filtering for disk event types.
Log Event When a User Exceeds the Warning Level – If quotas are enabled, an event is written to the system log on the local computer whenever users exceed their quota warning level. Administrators can view these events in Event Viewer, filtering for disk event types.

Configure and use disk quota in 2003
————————————
In Windows Server 2003 R2, just as in Windows Small Business Server 2003, the fsutil command provides a quick shortcut to quickly changing a specific user’s disk quota limits and warning levels.

Traditional Windows disk quotas are calculated using files’ logical size and are based on the user owning a file, not necessarily the user maintaining or storing the file.Windows Server 2003 R2 also includes a new feature that addresses several disk quota issues that is called File Server Resource Manager(FSRM).

Using Group policy
——————
Open the Group Policy Object Editor (gpedit.msc) and navigate to Computer Configuration > Administrative Templates > System > Disk Quotas > Enable
you can select 3 settings there
Allow processing across a slow network connection
Do not apply during periodic backgroun processing
Process even if the group policy object have not changed

Installing the File Server Resource Manager in 2008
—————————————————
Note:This feature is available in all editions of Windows Server 2008 except Server Core.

Server Manager > Roles > Add Roles > install the File Server role
After the file server role is installed
Server Manager > Features > Add Features > Remote Server Administration Tools Role Administration Tools > File Services Tools > File Server Resource Manager Tools. Select the File Server Resource Manager Tools check box, and then click the Install button.

Instead of specifying custom Quotas folder by folder, you can use standard FSRM Quota templates or define your own templates.
File Server Resource Manager > Quota Management > Quota Templates > Edit Template Properties

Advertisements

Posted on February 7, 2012, in Uncategorized, Windows. Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: