How to Audit File Server NTFS Permissions and Shares with PowerShell
Map NTFS permissions, share access, and ownership across file servers — perfect for audits, migrations, or cleanup projects.
Windows file servers tend to outlive every project that ever touched them. Shares get added, permissions get adjusted, and over time the actual access model on disk drifts away from what anyone remembers approving.
Whether you're preparing for a migration to SharePoint or Azure Files, responding to an audit request, or simply trying to clean up a messy file server, you need a clear picture of who has access to what.
PowerShell can do that — but only if you have a workflow you can rerun whenever the question comes up again.
What a permissions audit needs to capture
A complete file server audit usually includes:
- Share-level permissions
- NTFS permissions on top-level folders
- Inherited vs explicit access
- Group membership for assigned principals
- Folder ownership
- Sizes and last access timestamps for cleanup decisions
Why this work resists one-off scripts
Permission reports tend to grow. The first ask is usually simple. Then someone wants the data filtered differently. Then a new server needs to be included. Then someone wants ownership data added.
Each change tends to live in a slightly different version of the script. A workflow makes the logic easier to evolve in one place.
How PSForge helps
PSForge lets you assemble file server audit tasks visually and generate the PowerShell behind them. The result is a repeatable workflow you can point at any file server when the question comes up.
Example file server audit workflow
- Inventory shares on the target server
- Export share-level permissions
- Walk top-level folders and export NTFS permissions
- Resolve group memberships for assigned principals
- Capture folder ownership and last access data
- Flag broken inheritance and direct user ACEs
- Produce a structured audit report
Final thoughts
File server audits are often dreaded because they grow unpredictably. They don't have to be.
PSForge turns the work into a PowerShell workflow you can run, refine, and reuse — not rebuild every time.