Project context
Shared folders in a trading business accumulate order files, customer documents and operational records over years. In this case, the AD environment needed rebuilding while the file server contained roughly five years of ACL history. A blanket reset would have removed legitimate access while potentially preserving other undocumented grants. The project therefore treated identity reconstruction and permission remediation as one controlled migration.
Objectives
- Rebuild maintainable AD users, groups and OUs as the identity foundation for file access.
- Review about five years of ACL history without erasing everything at once.
- Move from direct user grants toward a security-group model that can be maintained and handed over.
Scope baseline
Inventory of shared folders, critical data, user/group relationships and ACLs.
Rebuild of AD users, groups, OUs and baseline policy.
Legacy ACL mapping, retain/remove decisions and staged permission changes.
Representative-user testing, rollback handling and permission-baseline handover.
Implementation and control
- 01
Export and review current folder ACLs, flagging critical folders, direct user grants and historical SIDs that no longer map cleanly.
- 02
Rebuild users, groups and OUs around the current organisation instead of copying old individual permissions blindly.
- 03
Create an “old ACL → new security group / approved exception” mapping and remediate known folders in controlled batches.
- 04
Test read, modify and create operations with representative users; if business access is affected, revert from the mapping rather than grant broad access.
- 05
Handover the new baseline, approved exceptions and the method for future joiner/leaver permission changes.
Risk and change control
Historical ACLs may include leavers, unknown SIDs or temporary grants and cannot be deleted without business confirmation.
When AD identities and file permissions change together, an explicit mapping is required to avoid accidental access loss.
Broad emergency grants can hide the real issue, so exceptions need an owner, reason and follow-up action.
Acceptance and handover
- The rebuilt AD user/group/OU structure supports normal identity administration.
- Critical shared folders have explainable group-based permissions or documented exceptions.
- Representative users verify core read, modify and create operations.
- Legacy ACL mapping, permission baseline and joiner/leaver maintenance method are handed over.

