Our file server is filling up because one department dumps everything.
FSRM (File Server Resource Manager) on Windows Server provides per-folder quotas and file screening with notifications to admin and user. Not just technical, also a conversation with the department manager.
Try this first
- 1Install File Server Resource Manager as a role feature, open the console.
- 2Define quota templates: e.g. 100 GB with soft warning at 80%, hard limit at 100%. Apply to specific folders (per department or project).
- 3Configure email notifications: user warning at 80%, manager notice at 95% and on hard limit.
- 4Use file screening to block known bulk files where they don't belong: no .iso, .mkv or .zip on a department share. Active screening blocks, passive only reports.
- 5Run a weekly storage report (FSRM has templates): top 10 largest folders, files older than a year, duplicates. Discuss with the department.
When to bring us in
If space stays tight, don't keep scaling out. Look into archiving cold data to Azure Files or SharePoint Online.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.