Windows Server 2022 — FSRM quota notifications stop firing on volume thresholds — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

FSRM quota notifications stop firing on volume thresholds on Windows Server 2022 disrupts operations and prevents the affected service from meeting its SLA until remediated.

Environment & Reproduction

The issue reproduces on Windows Server 2022 hosts where the storage subsystem is in use, typically following configuration drift or recent updates.

Get-FsrmSetting | Format-List
Get-WinEvent -LogName 'Microsoft-Windows-FileShareResourceManager/Operational' -MaxEvents 30

Root Cause Analysis

The defect stems from misaligned file server resource manager settings, missing prerequisites, or a corrupted state that blocks normal operation.

Quick Triage

Confirm the service is running and capture current configuration state before applying any change.

Get-FsrmQuota -Path 'D:SharesHR' | Format-List
Get-FsrmAction

Step-by-Step Diagnosis

Walk the storage stack from configuration to runtime, collecting logs and counters that point at the failing component.

Get-FsrmQuota -Path 'D:SharesHR' | Select Path,Size,Usage,Threshold
Get-WinEvent -LogName 'Microsoft-Windows-FileShareResourceManager/Operational' | Where Id -eq 12325

Solution — Primary Fix

Apply the corrected configuration and restart dependent services so the file server resource manager component re-initialises cleanly.

Set-FsrmSetting -SmtpServer 'smtp.contoso.com' -FromEmailAddress '[email protected]' -AdminEmailAddress '[email protected]'
New-FsrmAction -Type Email -MailTo '[email protected]' -Subject 'Quota Threshold Exceeded' -Body 'Path [Source File Path] has exceeded quota.'
Set-FsrmQuota -Path 'D:SharesHR' -Threshold (New-FsrmQuotaThreshold -Percentage 85 -Action (New-FsrmAction -Type Event -EventType Warning -Body 'Quota at [Quota Used Percent]'))
Restart-Service srmsvc

Solution — Alternative Approaches

Where the primary fix is blocked by policy or downtime windows, use the alternative configuration path or staged rollout below.

New-FsrmQuotaTemplate -Name '10GB Hard Quota' -Size 10GB -SoftLimit:$false -Threshold (New-FsrmQuotaThreshold -Percentage 90)
Update-FsrmQuota -Path 'D:SharesHR'

Verification & Acceptance Criteria

Confirm the service reports healthy state and end-to-end functionality succeeds against a representative workload.

Get-FsrmQuota -Path 'D:SharesHR' | Select Threshold,Action
Get-WinEvent -LogName 'Microsoft-Windows-FileShareResourceManager/Operational' -MaxEvents 10

Rollback Plan

If the fix introduces regressions, revert configuration to the pre-change baseline and restart the service to restore prior behaviour.

Remove-FsrmQuota -Path 'D:SharesHR' -Confirm:$false
New-FsrmQuota -Path 'D:SharesHR' -Template '100MB Limit Reports to User'

Prevention & Hardening

Bake the validated file server resource manager configuration into baseline GPOs or DSC and add a monitoring check for early detection.

Set-FsrmSetting -CommandNotificationLimit 60 -EmailNotificationLimit 60 -EventNotificationLimit 60
Get-FsrmQuota | Export-Clixml C:Backupfsrm-quotas.xml

Related Errors & Cross-Refs

Related: other storage failures, dependent service errors, and downstream client-side symptoms.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Windows Server 2022 and the relevant component, plus internal runbooks.