Effects of changing the Organization name

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.