This article was previously published under Q278365
This article has been archived. It is offered "as is" and will no longer be updated.
Disk quotas are a new feature in Windows 2000. This article discusses some of the considerations that you should look at when you are implementing disk quotas on Windows Clustering shared disks.You can enable disk quotas by accessing the properties of the disk volume in Windows Explorer, or through the Group Policy Object.
Method 1: Windows Explorer
Right-click the disk volume for which you want to enable disk quotas, and then click Properties.
On the Quota tab, click to select the Enable Quota Management check box.
Method 2: Group Policy Object
Set a Group Policy:
Click Start, click Run, type mmc, and then click OK.
In the Console menu, click Add/Remove Snap-in.
Click Add, click Group Policy under Available Standalone Snap-ins, and then click Add again.
In the Select Group Policy Object wizard, under Group Policy Object, leave the default location of Local Computer, and then click Finish.
Click Close, and then click OK.
Enable disk quotas on the Group Policy Object:
Under Console Root, expand Local Computer Policy, expand Computer Configuration, expand Administrative Templates, expand System, and then double-click Disk Quotas.
Double click Enable disk quotas, and then select Enabled
When you apply disk quotas to disks that may not always be available to the operating system (such as shared cluster disks), follow these steps:
On the Policy tab, select Enable.
Click to clear the following two check boxes:
Allow processing across a slow network connection
Do not apply during periodic background processing
Click to select the Process even if the Group Policy objects have not changed check box, and then click OK.
Restart the computer, or use the secedit command to refresh the policy. To do so, from command line, type:
secedit /refreshpolicy machine_policy
Use of Domain-Level Accounts
You should only use domain-level accounts when you assign the quotas, because local accounts would not be enforced when the disk fails over, which occurs because the other node would be unable to resolve the SID for the local account. For additional information, click the article number below to view the article in the Microsoft Knowledge Base: