Forum Discussion
Windows 2016 Server Long Path
What client OS has the problem?
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
Dave Patrick Windows 8 is now replaced with Windows 10https://shopfortool.com/gmail-sign-up-free-gmail-login-account-gmail-sign-in-on-www-gmail-com/ But all still work the samehttps://logingit.com/sign-office-365-office-365-login/ Just minor fixing.
- 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.I'd review the settings on the client. Also for the windows 7 clients this one might help.
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!
