A reddit dedicated to the profession of Computer System Administration • Community members shall conduct themselves with professionalism. • Do not expressly advertise your product. More details on the may be found. For IT career related questions, please visit Please check out our, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should read! Checkout the Users are encouraged to contribute to and grow our Wiki. So you want to be a sysadmin? Official IRC Channel - #reddit-sysadmin on Official Discord - •.

May 07, 2012 This is make sure that robocopy can be used to migrate my file server. There are quite a number of shared folder with extreme long file path. Else, shall I. Unable to delete a file or folder in Windows due to filename or path too long? Checkout Robocopy. Long path name support. Path too long? Use Robocopy. Jan 20, 2015 About File Name Issue by Robocopy. All of them are long file name. TechNet Subscriber Support in forum.

We have a Windows file share server set up on an Equalogic NAS box. We're migrating it over to actual Windows servers. They're running Server 2012 R2 Datacenter, and we're using robocopy for the bulk of the transfer.

I've come across hundreds or thousands of files that can't be moved because the file name is too long. Robocopy fails with error 123, and if I try to copy the files in Windows Explorer from the server itself I get 'file name is too long or invalid.' The kicker is that it really doens't even seem to be based off how long the file name. We'll have 4 files in the same directory with the same length names and only 2 of them will fail with this. Also you can still open the files. So if it's a text document I can open it in Word, copy and paste it into a new document, and save it to the new location.

Save As doesn't work. But I can't do this with thousands of files. How would you get around this problem? This is flat out wrong. Owens Sausage Pumpkin Patch. Windows has flavours of the Windows file APIs, one is legacy and limited to ~250 charterers, the other Unicode compatible one is not and is then limited only by the NTFS filesystem.

Robocopy uses the more recent API call, Explorer for whatever reason does not. You can force the use of the more modern API at the CLI by using absolute paths and prefixing them //?/ look at: You'll notice the robocopy /256 flag is specifically to turn OFF the default support of long file names. There is a very thorough explanation of what is going on here: • • • • •.