Three features can make a folder or drive “disappear” while the data still exists:

  • Folder Redirection changes a known-folder path to a network location;
  • Offline Files caches network content locally; and
  • Group Policy Preferences creates drive-letter mappings.

They share SMB and policy dependencies but hold different state. Diagnose them separately before copying anything.

Capture the effective paths

From the affected user’s session, record the known-folder path, UNC target, drive mapping, server/share resolution and the DC/GPO used. Capture gpresult and the relevant Group Policy/Offline Files events.

Check the user’s files in three places without changing them:

  • current network target;
  • local profile path; and
  • Offline Files cache/status through supported UI/tools.

Compare timestamps, sizes and hashes for representative files. Do not declare one copy authoritative because it is newest; disconnected edits can exist on both sides.

Diagnose reachability before permissions

Test DNS, SMB path and server/share availability using the UNC path. A mapped letter is session-specific and may not exist in an elevated process or policy context.

Microsoft’s Folder Redirection requires a UNC target. Do not redirect a known folder to a mapped drive or disable UAC to make that mapping visible.

If UNC works but the drive is absent, inspect the Group Policy Preference item, action, targeting and letter. Microsoft documents that “first available” drive-map behaviour can remove manual mappings from the selected letter upward. Understand the item before recreating every mapping.

Check policy and permissions together

Confirm the Folder Redirection GPO target, security filtering, setting and removal behaviour. Verify share and NTFS permissions for the actual user and folder, including ownership/inheritance design.

Do not seize ownership or grant Everyone/Domain Users broad access to fix one user. That may expose every redirected profile. Use a controlled administrative recovery identity only when policy and data ownership permit it, then return ACLs to design.

Protect Offline Files

If the client worked offline, its cache may contain the only recent edits. Do not reset/delete the cache, unjoin the domain or wipe the profile until content is reconciled and copied to protected storage.

Reconnect through the correct path, review Sync Center conflicts and resolve with the data owner. Record which version wins for each conflict. A green sync icon is not file-level proof.

Move or retire redirection deliberately

Folder Redirection settings can move content to a new location and define what happens when policy stops applying: redirect back to the local profile or leave the folder at the network location. These choices can copy large data sets and change where users work.

Before migration:

  1. inventory users, data size, open/offline clients and exclusions;
  2. build the target share with correct capacity/ACL/backup;
  3. reconcile Offline Files;
  4. pilot through normal policy processing;
  5. compare complete file manifests/hashes; and
  6. test policy removal and rollback.

Do not combine server cutover, GPO removal and local-profile cleanup in one irreversible step.

Verify access and data

Test sign-in and known folders from an existing and new device, online and approved offline mode. Verify create/edit/delete/rename, file ownership, drive mappings, application save/open, backups and restore. Confirm excluded users cannot browse another user’s folder.

Retain the old target read-only until user/data-owner acceptance and backup proof. Recovery is complete when the intended files are reconciled, permissions are least-privilege and policy consistently leads clients to the supported UNC destination.