Allow users to change the OneDrive folder directory (long company name issue)
The default folder for OneDrive (by design) creates a problem that it conflicts with the maximum 255 character path length issue.
For a persons business OneDrive area
C:\user\FirstnameLastname\OneDrive - LongCompanyName
For a Company Group/Team site
C:|users\FirstnameLastname\LongCompanyName\LongCompanyName - LibraryName
It means that you are massively restricted on how you can use OneDrive to avoid reaching the 255 character path length limit.
I contacted support and i am told this is "by design", it isn't really fit for the purpose, other cloud storage providers dont have this issue and allow you to change it, it is such a simple feature.
The whole idea of how OneDrive chooses where to place the files and how it keep track of what is being synchronized is completely wrong.
Just an example. I can't choose the name of the directory created by OneDrive. Some how, it crashed and lost what I was synchronizing. Now, it asks me to sign-in and by doing that, it wants to use another base directory, so the files I was synchronizing are not considered any more. I can change the path, but I have no control of of the name of target directoy!
More. What is the base idea of putting all the synchronized directories in only one place without any change to organizing it? This is so stupid! I have tens of synchronized folders and it is a mess to find anything.
Tom Kocmi commented
Having spaces in drive name is a terrible idea for those who use Windows Subshell for Linux
Alex M commented
Vote up this equivaent uservoice item.
Microsoft please consolidate these feature requests
Alex M commented
Hi. We have spaces and ampersand in our long company name. This is going to make migration from short (three character) homedrive difficult.
OneDrive=C:\Users\<userID>\AppData\Roaming\OneDrive\OneDrive - CompanyName & Co
OneDriveCommercial=C:\Users\<userID>)\AppData\Roaming\OneDrive\OneDrive - CompanyName& Co
OneDrive Group Policy allows us to
-Allow syncing OneDrive accounts for only specific organizations
-Set the default location for the OneDrive folder
But sync client appends an subfolder withcompany name. This is not necessary when only sync with one org and location has been specified.
Yes this. It causes a lot of confusion for end-users. If we want them to use the sync option to access files this should be looked at. Not every company is called Contoso.
There's a way to rename the displayed names on QuickAccess (reg hack with "LocalizedString"), but to get rid of spaces and to long names of the real folder name, the feature to rename (or chose an own folder name during the inital setup) an OneDrive folder is highly appreciated.
Is there anybody at Microsoft using OneDrive with multiple accounts/sync and NOT complaining?! :)
OneDrive is not usable for backups until this stupid issue is fixed.
80 characters Company Name, who has more*?
'OneDrive - HFTL Trägergesellschaft MBH Hochschule für Telekommunikation Leipzig'
* this is not fun, this is a serious concern!
Chris Meacher commented
I understand MS have little interest in solving this as it is "by Design", the point everyone is trying to make is this is an extremely poor design, as it severely limits usability and appears a relatively simple fix.
For each instance of the OneDrive app:
1) Keeping to the 256chr limit, add a string variable to be stored with each synced folder to store it's local root name
2) On startup check if this variable is set for each synced folder, if not then set based on default rules (to existing folders - nothing can have been changed by this point)
3) Add option in settings to rename the local sync instance
4) Validate rename entry for
(a) invalid entry - reject
(b) existing sync - warning / reject
(c) existing folder - ask if sync to contents of this folder instead (useful if had old link that broke)
5) temp desync to unlock existing folder, rename (or link to new folder), update variable, re-establish sync
Not only resolves issues on long tenant or folder names, but also of syncing same folder names from different locations on same site. E.g. If I wish to sync from following folders:
What I get locally is
-Tenant_Commercial - Latest
-Tenant_Commercial - Latest2
-Tenant_Commercial - Latest3
And no it's not poor structure - the ProjectA commercial lead needs to sync all of ProjA, the ProjectB lead, all of ProjB and so on, so it's set for the company requirements not my personal ones.
This additional option would allow the users to resolve both the really long tenant/folder names issue, and the duplicated folder names issue, and give the user much more control of how things are being saved to their local device...
This. I have to horizontally scroll to read my compiler's error messages because I store my code in your cloud.
David Tree commented
Have you not fixed this yet, wow, this is very frustrating for anyone working at a university of XXXXXXXXXX i need longer paths without spaces now please
John Stell commented
I thought microsoft would be no use. At first I thought I was wrong and OneDrive seemed useful. Not being able to rename the directory to one without spaces is just the kind of problem I feared in the first place. I now cannot use certain software without moving files around to avoid this. If I had a choice I would not be using this poor quality product.
David Foster commented
This is a severe restriction for those using specific programs that prohibit spaces in path names. I use GIS software specifically that cannot have spaces in path names, so to use OneDrive to backup these files, I have to move them out of OD, work with them, then put them back when done working. This defeats the whole purpose of OneDrive's live backup capability.
Our organization name length is 38 characters. We recently moved users over to Sharepoint from our file server, and many of our users are now running into file path length issues due to those 38 characters being added. Please provide an option to shorten that without impacting everything else in the tenant.
I have multiple domain names under one account. When setting up one drive I can't name the folders by domain or user name. That creates multiple one drive folders with the same name. Not good. Please look into changing this.
I don't get why any sane developer would create a restriction like this unless they were unaware of the competing path length limit. Using the company name (or "Personal") to distinguish one type of account from another is understandable as a default, but preventing people from changing/renaming the root folder is just unnecessary, especially if you don't even give account admins (e.g. the subscribed company's IT techies and the CEO above them) a choice in the matter.
If it were me, I would do away with BOTH restrictions:
1. let users change the default name of the folder (unless they are installing on company computers or otherwise subject to a domain's group policies, no one should be able to tell them what they can and cannot call a folder), and
2. remove the path length limit on the SharePoint backend (seriously Microsoft, it's 2020. Are you seriously telling me your commercial grade cloud servers can't afford to turn on "Enable NTFS long paths"? Next you'll tell me all your servers are actually smart-toasters with the latest version of Windows XP service pack 3 installed!)
Phillip M. commented
Fundamentally, this is a combination of two issues, both of which I think represent design oversights on the part of the application's development team:
1. The inability to use paths longer than a certain length, a constraint that hasn't been applied to offline Windows NT systems since... 98, I want to say? I don't know why this restriction would be imposed again short of #poorprogrammingpractices (we have 32 bit operating systems and in some case 64; why limit things to 2^8?), but I think it should be removed
2. The inability to fully customize the path of your OneDrive directory. You can customize everything above the company level and everything below the root of your site folder, but the directory names in between (company, group, and team) are chosen and not flexible because... reasons? Don't get me wrong, it's important to have a unique location for each site folder, but I think the top down policy needs to change; give users more control and let the current naming scheme just be the "default".
Issue #2 is actually what I came here to provide feedback about; I think it's silly, especially since it seems to be applied even to the personal edition of OneDrive. For instance, my personal account, despite being meant for individuals, forces the site folder to be named "OneDrive" even if I pick something like "D:/my cloud" in the "open file" window, resulting in "D:/my cloud/OneDrive". Why? Do you (as would be somewhat typical for Microsoft) not trust me to pick a unique name? Could you at least be consistent about it instead of naming the path different from the corresponding entry in my Navigation Pane (see screenshot for example of this inconsistency)?
Please fix this.
Craig Cowley commented
I mean this sounds like the same as this idea but with less votes - still needs to be implemented either way!
Another similar has been closed, but I need this possibility, seriously.
Please leave the decision to the user.