Forum Discussion
Solved
Effects of changing the Organization name
Hello. Our organization name is set up with a comma right now. I believe this drives the local OneDrive directory name (OneDrive - Name, Inc). If we edit the name to display without the comma, what w...
Renaming the OneDrive folder (actual path name) will not work as the client tries to "lock" the path. If the client is turned off, and then renamed - we will error out. You are able to change the friendly name of the entry that shows in file explorer, but note that this would not change the name that is accessible when navigating from command line.
The alternative here is renaming the tenant friendly name so the desired name can appear in all of the clients appropriately. However, we would not be able to smoothly transition for an already set up client. A client would need to a fresh setup, or be unlinked/relinked in order to handle the newly updated tenant name. Let me know if that helps!
Chris L.
Resurfacing this issue... We had the same problem: org name as originally entered was long and had a comma. Problems ensued, so we were prepared to resync as needed. However, following the org name change, attempted to unlink and relink (on Windows 10), ODFB still insists on a path with the old name. So, uninstalled OneDrive, removed the related registry entry, reinstalled OneDrive; still shows old org name in path. Tried reinstall a few times, adding reboots in the mix. Nothing worked. I am stymied how to change path name.
-Kelvin
-Kelvin
- Have you found the solution?
- kelvandy and Lpkkicpa, I can confirm that I to, tried every registry edit (service shutdown), explorer kill trick there is (and invented some new ones), including having to edit security zone keys and values (twice the headache). That could work for ONE boot instance, and only within Explorer. (Within a cmd.exe prompt, it did NOT really rename the file.) And on the next reboot, the "hot" security key is disliked by OneDrive's server services, and new connectors registry keys are generated, and the OLD-NAME comes back. Also, from fighting this, I can say I have an unwanted understanding of how the product functions- and fixing this is hard. Because clients can be "off" when the change is made, and MS would have to create a "name" sync mechanism to change the name, before then running its standard sync stuff, which in 5 years they have not done. But I can also attest that even UNSNYCING and UNLINKING all clients does not fix the problem. It appears you must actually delete the online account, and then recreate it. (which means all file sharing and associations have to be recreated, with new PIN authentication, the works.) I did not do that, but I did everything short of it. (If account deletion does not work, then nothing works.) Account deletion is in my opinion not a real solution. (If you had more than a few "OLD" users (like 2 of them), its unworkable. If you have a real organization change, and the name really NEEDS to change, Microsoft does not appear to be providing a solution of any kind. In 5 years. (This is a 2017 issue, and its 2022 now guys.) Where is the BEEF? Fire the product manager. Fire him or her, and get someone that understands priorities to run that program. Maybe take them out back first, before you fire them.
