They full on put what should be meta data into folder names then repeat the same crap into the file name just in case it gets accidentally moved or some crap logic like that. Thank you!Įdit: Thanks all for the great info, definitely have everything I need to tackle this user and get it resolved :) The team below me explained the limitation to the user and tried a few fixes (local GPO and registry change to allow long file paths), but for whatever reason those didn't work.Įither way, we don't have long file paths enable across the domain, I'm somewhat new to the position and am trying to figure out wouldn't it be enabled by default? there's got to be some major drawback right? Is it a security issue? Or that some apps may no be able to access the file because their own limitations to file paths? Is there something obvious I am missing? I want to make sure enabling this GPO to a test group and playing with it isn't going to be a waste of time.
Hi Sysadmin! I'm hoping to get some insight into a ticket I am currently working that was escalated to me from an irate user about not being able to access a specific file because the folder names include every detail about the project (and of course the file path is too long).
0 kommentar(er)
