If you’ve done many Windows file server migrations, you’ve certainly come across a long file path issue. There are a number of ways to address it.
For me, it’s preferable to know where the files are ahead of time rather than just stumble upon failures when running copies. Thankfully, Powershell can help us locate the long file paths with a 1-liner.
Get-ChildItem -Recurse | Where-Object {$_.FullName.Length -gt 260}