File paths exceeding 255 characters in Windows, Permissions getting corrupt. Solutions?

What do you do when you run into people that start using file paths on the file server where it exceeds 255 characters? Permissions start getting whacky and I typically just create a junction point or have them put file on SharePoint but I was wondering if one has a better solution to resolve this? We do not really have a good document management system besides using SharePoint.



Tell them not to.

In Windows, I can create a share which goes deep into one of the long paths, just reducing the path length on that share. But that's not a very good solution.



Tell them not to.

In Windows, I can create a share which goes deep into one of the long paths, just reducing the path length on that share. But that's not a very good solution.



Yeah I agree unfortunately these are people who don't take "no" for an answer: "make it work"....



The users may have to tell MS to "make it work" as most apps can handle long file names but the OS is the bottleneck. Have you considered a re-org of your directory structure?

Haven't used the following tool but you may want to take a look as a potential fix.
http://longpathtool.com/



There is no good solution other than slapping your user's hand



Share this

Related Posts

There was an error in this gadget