Forum Discussion
Files On-Demand for macOS QA
Working on OneDrive is simply a nightmare! Why must you create a copy inside ~/Library/CloudStorage/ anyway? Can't you make it simpler as it could be? I would never choose OneDrive if it were our institution that only allows OneDrive as the sole cloud storage plan. Can you just learn from Dropbox, keep it as simple as it can, with a folder simply synchronized between local drive and the cloud?
Also, it is EXTREMELY unprofessional to mandatorily name the folder to be OneDrive - XXX, with space and dash in there! Please, remove the space, and let us choose what we want to name the OneDrive folder, please, please, please!!!!
Then, since I have the unlimited quota, I want to have my external hard drive synchronized to OneDrive cloud storage. Guess how many OneDrive-related folders would OneDrive create for me? THREE!!! There is 1) one inside my external drive, which links to 2) ~/Library/CloudStorage/, and 3) one hidden .ODContainer. Man! Microsoft is really obsessed to get people confused for all those years. Here is a fun read of the instruction:
Using another volume
Sometimes, users choose a path on another volume to set up OneDrive. A typical use case for this happens when a user has a small internal drive on their Mac, but also has a larger external drive attached.
This configuration is still supported in the new Files On-Demand experience if an external drive is selected during the first-run experience. A few things change as a result:
The sync root remains in ~/Library/CloudStorage, on the user’s home volume. As noted above, this path cannot be moved from this location.
The cache path is on the volume that was selected during the first-run experience. This is located in a hidden folder that’s a sibling of the location that was chosen.
This folder begins with the name “.ODContainer”.
A symlink is created from the chosen location to ~/Library/CloudStorage.
For example, if the user selects /Volumes/BigDrive/OneDrive for their OneDrive path:
The sync root will remain in ~/Library/CloudStorage/OneDrive-Personal
The cache path will be set up at /Volumes/BigDrive/.ODContainer-OneDrive
A symlink will link from /Volumes/BigDrive/OneDrive to ~/Library/CloudStorage/OneDrive-Personal
Because the cache path is located on an external drive in this scenario, any pinned content will be stored there and not on the main drive.
The cache path folder is hidden by default. Users should not modify this folder or its contents.
Really? Can you just let us to create our own OneDrive-folder, and just keep everything inside this folder to be synchronized with the cloud copy, regardless of file types, drive types, where this OneDrive-folder is located at? Can't you learn something from Dropbox??? Do you have to make such a simpler idea so complicated????????