A folder copy is not proof that a file server migration preserves permissions. Share names, local paths and filesystem permissions must be linked. This inventory reads existing settings without removing shares or assigning new permissions.
1. Identify the server and scope
Record computer name, domain or workgroup, Windows 2000 edition, service pack and date. Use authorized access and an existing backup. Open Computer Management through Administrative Tools and verify the selected target computer. Do not change network protocols or security policies for the inventory.
2. Create one row per share
Open Shared Folders and Shares. Record name, local path and description. Flag administrative shares separately rather than automatically migrating them. Open a business share’s properties read-only and record every displayed group or identity with Allow or Deny permissions. Close without applying changes. Do not disconnect sessions or close open files.
3. Inspect the NTFS layer separately
In Explorer, open the local source folder’s Properties and Security. Record filesystem, owner and visible permission entries; under Advanced, include scope and inheritance where displayed. Sample subfolders with different requirements. A screenshot of the root folder does not prove identical permissions throughout. FAT/FAT32 has no NTFS file permissions; mark that explicitly.
4. Map identities and exceptions
Distinguish local server accounts, domain accounts and groups. Identical names on two servers do not establish identical identities. Preserve unresolved SIDs as open mapping issues; do not delete them or replace them with Everyone. List service accounts, encrypted files and exceptional subfolders as separate checks. Do not put credentials in the inventory.
5. Prepare verifiable migration evidence
Link share, path, share permissions and NTFS evidence with a unique identifier. Record owner, capture time and unresolved questions. An Explorer copy can inherit different permissions; copying to FAT does not preserve NTFS security information. Select the later copying method separately for the actual versions. After migration, use representative authorized and unauthorized test accounts to check both allowed and denied access. An inventory alone is not a successful migration test.
