asked on How to prevent users from exceeding the long file path name limit
Hi,
Our terminal server users are constantly naming files with names that exceed the long file path name limit which then prevents users from accessing or moving the file. We are currently only able to react to the issue after the naming has taken place, are there any proactive solutions that prevents or warns users when they attempt to name a file which will then exceed the long file path name limit.
Has anyone created any Powershell scripts which have resolved the above issue?
Our terminal server users are constantly naming files with names that exceed the long file path name limit which then prevents users from accessing or moving the file. We are currently only able to react to the issue after the naming has taken place, are there any proactive solutions that prevents or warns users when they attempt to name a file which will then exceed the long file path name limit.
Has anyone created any Powershell scripts which have resolved the above issue?
Powershell
Last Comment
Server Guy
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks for you above comments, I will continue to investigate.
ASKER
Will continue researching whilst educating our users.
The problem is "what actually is the file path length"? Well, "it depends" - again, otherwise users wouldn't be able to save files that other users won't be able to access.
There's the absolute file path on the server - that is usually already longer than what the user sees.
Then with access over shares, the path length to the same file will vary, depending on where the drive letter is mapped, or whether a UNC was used.
You'll need to educate your users, until Microsoft and all other developers will fix all their products.