Windows Server 2008: compare shares and permissions before file-server migration

Before copying, establish a traceable source-to-target comparison. This guide builds the review framework; it does not cut over a file server.

1. Define the source

Record server version, volumes, local data paths and owners. In Computer Management, read Shared Folders and the shares list. Capture share name, UNC path, local target and purpose. Distinguish administrative shares from user data. Flag DFS, quotas, shadow copies and applications separately.

2. Record both permission layers

Read share permissions and, separately, NTFS security on data folders. Record users/groups, identity/SID, allow/deny, inheritance and exceptional subfolders. Matching display names do not prove matching identities: local accounts belong to their computer. Do not remove unresolved SIDs or guess replacements.

3. Build a target matrix

Map each source share to proposed destination path, name, capacity and identities. Identify UNC references in logon scripts, applications and shortcuts. EFS-encrypted files, live databases and vendor services need separate preservation and transfer procedures. A copying tool alone does not cover them.

4. Plan representative tests

Use working copies in a separate test environment to check reading, creation, modification and expected denial with suitable test identities, not only an administrator. Compare tree structure, error logs and selected contents; file counts and sizes alone do not prove completeness. Leave production permissions unchanged.

5. Approve cutover separately

Record unresolved differences, backup, rollback and acceptance criteria. Write freezes, final synchronization, renaming and shutdown belong to a separately planned migration. Linked historical Microsoft guides concern specific destination versions, not a blanket recommendation to move to Server 2012 R2 today.

Sources