{"id":35111,"date":"2022-02-24T15:24:55","date_gmt":"2022-02-24T20:24:55","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=35111"},"modified":"2022-10-28T07:45:08","modified_gmt":"2022-10-28T11:45:08","slug":"onedrive-root-change-and-files-on-demand","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/02\/24\/onedrive-root-change-and-files-on-demand\/","title":{"rendered":"OneDrive Root Change and Files On-Demand"},"content":{"rendered":"

Adam Engst<\/a>:<\/p>\n

I don’t use OneDrive, but users are up in arms after its most recent update made the Files On-Demand approach mandatory, removing the option to keep all files local with a single switch. Microsoft explained this move<\/a>, but users remain unhappy<\/a> for a variety of reasons.<\/p>

The workaround seems to be to “pin” files or folders, which keeps them local. If you want everything local, you have to pin all your top-level folders. Unfortunately, and this is causing consternation for users who have vast amounts of data stored in OneDrive, that means you have to redownload everything from the cloud.<\/p><\/blockquote>\n\n

Tim Hardwick<\/a>:<\/p>\n

\n

What this has meant in practice for many users is that any local copies of files synced to OneDrive have been summarily wiped from their Mac since the update was rolled out.<\/p>\n

[…]<\/p>\n

On top of these errors, some users are also experiencing problems with files refusing to download or open correctly in their default application.<\/p>\n<\/blockquote>\n\n

Tim Hardwick<\/a>:<\/p>\n

In an update<\/a> to its original blog post introducing this aspect of its new “Files On-Demand Experience,” Microsoft has now responded to these concerns by explaining that the first version of Files On-Demand is built on several pieces of technology that are now deprecated by Apple in macOS 12.3, currently still in beta.<\/p><\/blockquote>\n\n

John C. Welch<\/a>:<\/p>\n

\n

I don’t have a problem with FOD as a concept, but I had it turned off for specific reasons, one of which is that I regularly work disconnected, which makes FOD kind of useless.<\/p>\n

[…]<\/p>\n

OneDrive and FOD are at this point lying to me. It’s not even completely downloading the file placeholders<\/em> for folders until you click on them. So if you weren’t aware of this, and were offline and clicked on a FOD’d folder, you’d think it was empty, that you had lost data<\/em>.<\/p>\n<\/blockquote>\n\n

John C. Welch<\/a>:<\/p>\n

\n

To be blunt: were a random script or executable do what OneDrive is doing here, namely deleting data without so much as a warning, we would call that script malware<\/em> and warn the world about it so suitable countermeasures could be implemented. That OneDrive gives you an as yet manual method to eventually get all the files that were already local<\/em> back to that benighted state doesn’t change the malware-like behavior OneDrive is engaging in here.<\/p>\n

[…]<\/p>\n

[Apple] required you to move the OneDrive folder, they most certainly did not make you force everyone to Files-On-Demand, insinuating otherwise is quite insulting to your customers’ intelligence.<\/p>\n<\/blockquote>\n\n

John C. Welch<\/a>:<\/p>\n

\n

Using OneDrive on an external drive is now a real<\/em> problem, one that may not be fixable<\/p>\n

A lot of workflows that depended on those files being in a specific place are broken<\/p>\n

[…]<\/p>\n

The OneDrive root change alone<\/em> will take months to sort out, along with any bugs caused or discovered. Throwing the FoD change on top of it was just foolishness<\/p>\n

[…]<\/p>\n

In any event, even though I know for a fact that the problems people are seeing now were reported during the beta cycle, I think the team either blew off the data[…]<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n