Forum Discussion
Silvan Diem
Jul 13, 2018Copper Contributor
Windows 2016 Server Long Path
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 Windo...
Silvan Diem
Copper Contributor
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.
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.
Dave Patrick
Jul 15, 2018MVP
I'd review the settings on the client. Also for the windows 7 clients this one might help.
- Silvan DiemJul 16, 2018Copper Contributor
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!