Applies to: Windows Server 2019, Windows Server 2022 and Windows Server 2025, subject to the workload and edition requirements below.
Use quotas to manage a folder, not just a disk
File Server Resource Manager quotas measure and optionally limit the space consumed beneath a folder. They are useful when departments share a volume but need separate capacity policies. A soft quota records usage and triggers configured notifications without blocking writes. A hard quota enforces its limit and can cause an application save to fail. Start with observation when the application behaviour and growth pattern are not yet understood.
FSRM folder quotas differ from NTFS per-user disk quotas. Choose the mechanism that matches the accountability model rather than enabling both by habit. This guide establishes a soft quota for D:\Shares\Finance, adds an event notification and then explains how to move to enforcement deliberately. It is not a substitute for volume-capacity monitoring: several folders may stay within their quotas while the underlying volume still fills because of backups, logs or other data.
Confirm NTFS and measure existing consumption
FSRM supports NTFS volumes, not ReFS. Check the actual file system before installing the role or creating policy. A failure to apply a quota to ReFS cannot be solved by repeatedly recreating the object. Moving a workload between file systems is a separate migration with compatibility and backup requirements. Also identify parent quotas, because a folder can be constrained by a quota higher in its path.
Document the business owner, intended capacity, observed growth and the response to a warning. A threshold is useful only if somebody receives and acts on it. Leave space for temporary application files and peak imports. For an existing folder, capture current usage through FSRM after the initial scan rather than relying exclusively on a quick recursive file-size sum, which can differ from quota accounting and may encounter inaccessible paths.
Get-Volume -DriveLetter D | Select-Object DriveLetter,FileSystem,SizeRemaining,Size
Test-Path -LiteralPath 'D:\Shares\Finance'
Get-WindowsFeature -Name FS-Resource-Manager
Install the role and review existing policy
Run the installation from an elevated Windows PowerShell session. Include management tools so that File Server Resource Manager is available for visual inspection of quotas, thresholds and reports. Review the installation result for success and any restart requirement. Do not restart a production file server without coordinating open-file and application impact.
Install-WindowsFeature -Name FS-Resource-Manager -IncludeManagementTools
Import-Module FileServerResourceManager
Get-Service -Name SrmSvc
Get-FsrmQuota | Select-Object Path,Size,Usage,SoftLimit
Get-FsrmAutoQuota | Select-Object Path,TemplateLook for an existing quota on Finance and any auto-apply quota on its parent. Auto-apply quotas create policy for child directories and are useful for home folders, but they are not the same as one quota that caps an entire department tree. Avoid creating a second policy whose interaction with an existing parent quota has not been reviewed. Preserve the baseline configuration through the FSRM console or approved export process before changing production settings.
Create a meaningful warning threshold
The following event action writes a warning when usage passes 85 percent. It avoids embedding SMTP credentials or depending on mail delivery for the first pilot. Use an approved monitoring system to collect and alert on the event. Customize the text so operators know which owner and capacity policy apply. FSRM expands its bracketed variables at notification time.
$eventAction = New-FsrmAction -Type Event -EventType Warning `
-Body 'Finance storage warning: [Quota Path] is at [Quota Used Percent]% of [Quota Limit MB] MB. Contact the Finance storage owner.'
$threshold = New-FsrmQuotaThreshold -Percentage 85 -Action $eventAction
New-FsrmQuota -Path 'D:\Shares\Finance' -Size 100GB `
-SoftLimit -Threshold $threshold `
-Description 'Finance capacity pilot; review before enforcement'The PowerShell size suffix uses binary units, so record the displayed configured capacity clearly when communicating a business limit. A soft quota may exceed 100 percent and continue growing. The example does not create an email action; email notifications require FSRM mail settings, a permitted relay path and a real delivery test. A command action introduces additional execution and privilege considerations and should not be added merely to delete files automatically.
Verify quota state and notification delivery
Inspect the specific object rather than relying on the presence of the feature. Confirm that Path identifies the intended folder, Size is the approved value, SoftLimit is True and the threshold contains the expected action. Allow the service to finish initial accounting, especially on a large tree, before treating an early usage figure as final.
Get-FsrmQuota -Path 'D:\Shares\Finance' | Format-List Path,Description,Size,Usage,SoftLimit,Threshold
Get-WinEvent -FilterHashtable @{LogName='Application';ProviderName='SRMSVC'} -MaxEvents 20If no events exist yet, that alone is not a failure: a threshold may not have been crossed. Test notification delivery using a dedicated test folder and a small disposable quota rather than filling the production share with test files. Confirm that the event reaches the operator’s actual alert queue. Keep the volume’s remaining free space visible throughout testing, and remove test content after the result is recorded. Never create a test that risks exhausting the disk beneath real users.
Move from observation to enforcement deliberately
Collect usage across a meaningful business cycle, including month-end or import peaks. Review the proposed hard limit with the data owner and application owner, and define a response when writes are blocked. Reducing a limit below current usage does not clean up files; it prevents additional growth and can interrupt work. Make the required space available or agree on retention actions before changing the limit.
# Run only after the hard-quota change has been approved:
Set-FsrmQuota -Path 'D:\Shares\Finance' -Size 100GB -SoftLimit $false
Get-FsrmQuota -Path 'D:\Shares\Finance' | Select-Object Path,Size,Usage,SoftLimitSet a warning comfortably below enforcement so there is time to respond. Test the actual application’s behaviour when space is refused using a non-production folder. Some applications save through temporary files and need headroom greater than the final document size. Others report a generic save failure that users interpret as permission loss. Document the expected error and escalation route before enforcing the policy on important workflows.
Diagnose blocked writes and unexpected usage
If a user cannot save while the Finance quota appears to have room, inspect quotas on parent folders and the underlying volume free space. An ancestor quota can impose a smaller effective allowance. Also check NTFS permissions, file screens, locks and application errors. A quota is not the only cause of a disk-full message, and an access-denied message does not prove a quota fault.
If quota usage looks stale, check SrmSvc, recent FSRM events, the volume file system and whether an initial scan or rescan is still running. Inspect the path carefully after a volume or directory migration. For missing notifications, verify the threshold crossing, action configuration, event collection and SMTP relay if used. Avoid changing service-account permissions or deleting FSRM metadata as an early troubleshooting step; retain configuration and error details for a supported repair.
Rollback and maintain the capacity policy
To stop enforcement while retaining measurement, set SoftLimit back to True on the specific quota. If the quota was created in error, Remove-FsrmQuota -Path D:\Shares\Finance removes that policy object after review; it does not delete the folder or recover free space. If policy derives from a template or auto-apply rule, correct the source policy as well, or it may be reapplied later.
Record changes to limits, owners and threshold actions. Review the quota when staffing, retention or application behaviour changes, and test notification delivery periodically. Keep disk-capacity alerts separate from quota alerts so neither depends on the other. When a hard quota blocks work, preserve user data and identify a justified capacity or retention response rather than removing files indiscriminately. A useful quota makes growth predictable and actionable while keeping its operational consequences understood.
Related guidance and official references
Install the File Server role; Create a secure SMB share; Measure disk performance.