Short answer: A network audit should account for permissions, network activity and the share owner's retention rules.
By DiskAnalyzer editorial resource · Published 2026-10-05 · Documentation reviewed 2026-10-05
When this guide is useful
Schedule a large inventory outside the busiest period when possible. Keep filenames private and document the user context so the storage administrator knows what the report actually covers.
Recommended workflow
- Confirm authorization and scope.
- Scan a specific share or folder.
- Note inaccessible paths.
- Share findings with the storage owner before cleanup.
Limits and precautions
A client's view can omit data it cannot access, so do not treat it as a server-wide total.
Keep a useful record
Record the drive or folder, scan time, application version and the measurement you used. Keep observations separate from proposed changes. If a result leads to a cleanup, record the file owner, backup status and actual free-space change. This makes the result easier to review and helps explain differences in a later scan.
Quick review checklist
| Question | What to record |
|---|---|
| What did you inspect? | The exact volume or folder, not just the PC name. |
| What action is justified? | Share findings with the storage owner before cleanup. |
| What could go wrong? | A client's view can omit data it cannot access, so do not treat it as a server-wide total. |
Next steps
If the result is unclear, preserve the current report and narrow the investigation to one folder or application. Make one approved change at a time, then repeat the relevant measurement. Avoid presenting a predicted saving as a measured outcome.
Related guides
- Audit an External Drive with WizTree
- Find Large Files on a USB Drive
- Find Which Game Library Uses the Most Space
- Plan a Useful WizTree CSV Inventory
Download information · How we verify guidance
Sources and verification
- WizTree developer documentation
- WizTree developer FAQ
- WizTree developer download notes
- Microsoft Windows storage guidance
Prepared from public documentation and practical storage-audit reasoning. No hands-on Windows test or independent binary inspection was performed for this publication. Menu names and package requirements can change; check the developer documentation for your installed version.