Home

Windows 2016 Server Long Path

%3CLINGO-SUB%20id%3D%22lingo-sub-215281%22%20slang%3D%22en-US%22%3EWindows%202016%20Server%20Long%20Path%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215281%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20would%20like%20to%20migrate%20from%20Windows%202008%20R2%20File%20Server%20to%20Windows%202016%20Server%20(Version%201607%20OS%20Build%2014393.2363).%3C%2FP%3E%3CP%3ENow%20we%26nbsp%3Brecognized%20that%20there%20must%20be%20a%20new%20limitation%20on%20the%20path%20length%20in%20Windows%202016%20Server.%3C%2FP%3E%3CP%3EOn%20the%20Windows%202008%20Server%20we%20could%20access%20path%20longer%20than%20260%20characters%20whitout%20any%20problem.%20(Shared%20folder%20over%20the%20network%20or%20on%20the%20server%20with%20explorer.%20)%3C%2FP%3E%3CP%3EWe%26nbsp%3Benabled%20the%20GPO%20Setting%20%3A%20%22Enable%20Win32%20long%20paths%22%20-%20without%20success.%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20workaround%20or%20is%20it%20impossible%20to%20move%20data%20with%20long%20path%20without%20substitute%20the%20path%20with%20shortnames%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BAny%20kind%20of%20help%20is%20highly%20appreciated%3C%2FP%3E%3CP%3EThanks%20in%20advance!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-215281%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215994%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%202016%20Server%20Long%20Path%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215994%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3EFound%20the%20Solution%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.pelegit.co.il%2Fenable-long-path-windows-server-2016%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.pelegit.co.il%2Fenable-long-path-windows-server-2016%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20to%20activate%20shortnames%20on%20tthe%20server%20on%20the%20apropriate%20volume%3A%3C%2FP%3E%3CP%3Efsutil%208dot3name%20set%20d%3A%200%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%26nbsp%3B%20i%20copied%20the%20Data%20again%20from%20the%20Source%20Fileserver%2C%20everything%20works%20as%20expected%20with%20all%20the%20Windows%20Clients!%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20To%20all%20for%20your%20help!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215780%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%202016%20Server%20Long%20Path%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215780%22%20slang%3D%22en-US%22%3E%3CP%3EI'd%20review%20the%20settings%20on%20the%20client.%20Also%20for%20the%20windows%207%20clients%20this%20one%20might%20help.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2891362%2Fa-file-copy-operation-fails-when-files-or-folders-have-long-paths-in-w%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2891362%2Fa-file-copy-operation-fails-when-files-or-folders-have-long-paths-in-w%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215779%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%202016%20Server%20Long%20Path%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215779%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20rrply.%3CBR%20%2F%3EWe%20have%20a%20mixed%20environment%20witj%20Windows%207%2F10%20Clients.%3CBR%20%2F%3ENow%20we%20like%20to%20migrate%20our%20Fileserver%20W2K8%20R2%20to%20W2k16%20.%20When%20we%20copied%20the%20filestructure%201%3A1%20to%20a%20Winows216%20Server%3A%20The%20Windows%2010%20Clients%20see%20and%20access%20Filepaths%20deeper%20256%20chars%20but%20not%20create%2Fmodify%20files%20in%20that%20path.%20Window%207%20can't%20see%20files%20deeper%20256%20chars.%3CBR%20%2F%3EWith%20the%20old%20fileserver%202k8R2%20we%20had%20not%20this%20Problem.%20Why%3F%20What%20has%20changed%20%3F%20What%20is%20the%20recommended%20procedure%20to%20migrate%20a%20fileserver%20!%20could%20someone%20help%3F%3CBR%20%2F%3EThanks%20in%20advance.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215398%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%202016%20Server%20Long%20Path%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215398%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20client%20OS%20has%20the%20problem%3F%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.howtogeek.com%2F266621%2Fhow-to-make-windows-10-accept-file-paths-over-260-characters%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.howtogeek.com%2F266621%2Fhow-to-make-windows-10-accept-file-paths-over-260-characters%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Silvan Diem
Occasional Contributor

We would like to migrate from Windows 2008 R2 File Server to Windows 2016 Server (Version 1607 OS Build 14393.2363).

Now we recognized that there must be a new limitation on the path length in Windows 2016 Server.

On the Windows 2008 Server we could access path longer than 260 characters whitout any problem. (Shared folder over the network or on the server with explorer. )

We enabled the GPO Setting : "Enable Win32 long paths" - without success. 

Is there a workaround or is it impossible to move data with long path without substitute the path with shortnames ?

 

 Any kind of help is highly appreciated

Thanks in advance!

 

 

4 Replies
Highlighted
Highlighted
Thanks for the rrply.
We have a mixed environment witj Windows 7/10 Clients.
Now we like to migrate our Fileserver W2K8 R2 to W2k16 . When we copied the filestructure 1:1 to a Winows216 Server: The Windows 10 Clients see and access Filepaths deeper 256 chars but not create/modify files in that path. Window 7 can't see files deeper 256 chars.
With the old fileserver 2k8R2 we had not this Problem. Why? What has changed ? What is the recommended procedure to migrate a fileserver ! could someone help?
Thanks in advance.
Highlighted

I'd review the settings on the client. Also for the windows 7 clients this one might help.

https://support.microsoft.com/en-us/help/2891362/a-file-copy-operation-fails-when-files-or-folders-h...

 

 

 

 

Highlighted

Hi, 

Found the Solution here: https://www.pelegit.co.il/enable-long-path-windows-server-2016/

 

Have to activate shortnames on tthe server on the apropriate volume:

fsutil 8dot3name set d: 0

 

After  i copied the Data again from the Source Fileserver, everything works as expected with all the Windows Clients! 

Thanks To all for your help!

Related Conversations
SharePoint 2016 / sharepoint online
Share24x7 in SharePoint on
1 Replies
Multi table query
sundarzee in Access on
3 Replies
Exchange 2016 OnPrem - cutover migration - split company
leffa in Exchange on
2 Replies