The problem
Application documents lived on a separate server from the main file server, and the decision was to keep one copy of the data on the main server. Share permissions had also picked up leftovers such as disabled accounts and orphaned entries.
What I did
- Moved the document shares onto the main file server, pre-seeded the data with Robocopy, and copied the original permissions.
- Published every app share through a DFS namespace path, so apps no longer depend on which server holds the data and a future server replacement is a one-line change.
- Pointed links at fully qualified names so both Windows and Linux hosts can use them.
- Removed a dead namespace target and an orphaned namespace object from the directory, after confirming nothing used them and backing them up first.
- Cleaned up permissions on engineering and customer files: removed disabled accounts and an orphaned entry, and limited an automation account to the read access it needed.
- Rolled out a scheduled mirror task that keeps each server’s local copy of the in-house app suite matched to the master share, parking local-only files instead of deleting them.
Outcome
Apps reach their documents through stable namespace paths and permissions are cleaner. The final data sync for the last two app shares is set for an evening the app owner picks.