Question: Run a recursive duplicate scan for the overlapping O: and R: root names, then migrate the workflow into a remote-friendly package and test it.

Completed work:

• Built a remote-friendly Windows package at C:\Users\SAguiar\Documents\Migration docs\server-cleanup\Servers Cleanup Repo\scripts\remote\admin-root-recursive-duplicate-scan.
• Verified the package locally with UNC roots using Test-Environment.ps1 against \\server02\C$ and \\server04\C$.
• Ran the recursive overlap scan successfully for 17 of the 18 overlapping top-level names and saved outputs under C:\Users\SAguiar\Documents\Codex\drive_indexes\o_r_recursive_overlap_scan_20260429_223109.
• Built the workbook C:\Users\SAguiar\Documents\Codex\drive_indexes\o_r_recursive_overlap_scan_20260429_223109\O_R_recursive_overlap_scan_2026-04-29.xlsx.

Key findings:

• Completed overlap roots: 17
• Pending overlap root: Windows
• Exact duplicate rows: 5718
• Path difference rows: 60842
• Hash skip rows: 60
• Enumeration error rows: 11
• Top exact-duplicate roots: Users (3845), ProgramData (1009), Program Files (505), Program Files (x86) (347)
• Largest divergence root: Users (32528 left-only, 20723 right-only, 462 same-path different-hash, 256 same-path different-size)

Scope notes:

• The recursive comparison was limited to the shared immediate top-level names.
• For matching folders, the duplicate boundary was the same relative path on both sides.
• Equal-size file pairs were hash-confirmed with SHA-256.
• Cross-path duplicate hunting inside giant system trees was intentionally not attempted.