How to get out of the situation with a lot of subfolders on a file server?


There is a file server to WinSrv12r2

The employee has created in the folder structure of 8 levels (subfolders)
Accordingly, the activated limit Win 256 characters in the file path and nothing works

What are the ways out of situation, but to prohibit such a structure (assuming that he really needed) ?
March 23rd 20 at 19:13
6 answers
March 23rd 20 at 19:15
Translate file storage with NTFS on the new ReFS. There the problem is solved.
March 23rd 20 at 19:17
I believe in this only if he is a biologist there, like unit-suborder-Spodoptera-family-blablabla. In otdelnyh cases there the structure is simple curve and make all the arrangements on the sane level of nesting.
Judging by the dock really is the limit to 260 characters. Ie ntfs allows you to fence the long way, but the software that uses the win api cannot correctly to work with it. In later versions of win10(and the expected win server) this restriction is not available.
I will answer all right _))

Thanks for the comments, but
1. Moving on to another Axis not an option
2. The removal of restrictions is also not an option, because the data folders are processed (optionally), that doesn't take way more than 244 characters
3. Concerning need, I'll try to explain. It may be a bright idea _))
This is the working folder of the project Manager (first level Project), a large project is made up of small (second level - mini-projects), some Small projects consist of several projects (the third level is the Micro-project).
And each project has it's own structure (4th, 5th etc)

To make each project (Mini or Micro) on the upper level is not an option, because projects of the 1st level we have 100ни and what the group needed - lelia_Kohler commented on March 23rd 20 at 19:20
Concerning need, I'll try to explain. It may be a bright idea _))
In such cases typically use the database. Or a special system database. And keep all files in one folder. - Ramon26 commented on March 23rd 20 at 19:23
@Ramon26, this section quickly to raise SharePoint _)) - lelia_Kohler commented on March 23rd 20 at 19:26
March 23rd 20 at 19:19
May have to share the destination folder and the path will ipadress/endfolder
March 23rd 20 at 19:21
It's probably easier to talk to the user, than disable. And so, you can try to remove the restriction on the long path:
March 23rd 20 at 19:23
The only working solution is to switch to Linux. But I have my suspicions that this option does not suit you. Therefore, it remains only to carry out user conversation that no need to do so. Another universal solution at the moment, I do not know. Even if you have the latest Windows 10 and you removed the limit via the registry or group policy, it still will not work properly. Yes, the guide will allow you to manipulate files and folders, but even the newest Excel cannot open a spreadsheet and Acrobat Reader will generate an error when opening the PDF file.

You can use crutches. For example, to pick up ON that correctly digest a long journey. Or reduce nesting by using the command subst. Or mount the folder as a network drive. Or to teach the user to use the UNC format \\?\Drive:[\Directory][\File]. Or change the way file storage. Or...
March 23rd 20 at 19:25
What are the ways out of situation, but to prohibit such a structure (assuming that he really needed) ?
  • To share the underlying folder, the path will be shorter.
  • Use shorter names.
  • To explain to the user that there are other ways of grouping files.

Find more questions by tags Windows ServerData storageWindows