My experience with the new OneDrive Team Site Sync

Joel Parmer No resolution yet. We noticed that if you Save As a word document into local OneDrive Sync directory, it successfully uploads to Sharepoint online, but if you edit a document already synced or copy a document into the directory from e.g., desktop. It fails to upload as well. 

So far we have noticed that with even the latest version on a fresh computer the Sync works perfectly. However we do not want to get an influx of overwritten files in the Sharepoint Online library, if we reinstall OneDrive on one of the faulty computers. 

The curious thing though - In one location (15 users with computers total), so far five users have experienced this issue, rest of them have Sync working with no problems whatsoever.

We keep trying different scenarios, to workaround this overwrite issue.

P.s. downgrading to a earlier version did not help at all - we copied over the %localappdata%/Microsoft/OneDrive/17.3.6720.1207 folder from a fresh install machine, used registry to add version Key, and InstallPath/InstallPaths strings. And modified the "CurrentVersion" and "CurrentVersionPath" with the previous version.

Settings --> About displayed the correct version 17.3.6720.1207, however this did not help.

This just cropped up for us today as well.  Was there a fix for this?  Anyone else seeing it?

Greetings Rob-CTL

Whilst I was testing out on a brand new machine with the user account, I noticed that I keep receiving new files, that are being downloaded. And I confirmed with users, that they keep saving documents locally on the Synced OneDrive folder. 

After performing an additional test, turns out only the download of new versions from SharePoint Online is broken. 

Just to let you know, that everything might not yet be lost, since the edited files sucessfully upload to the Cloud. 

Crisis is partially averted, now to re-sync everything and check if download works as intended. 

Thank you for your help.

Deleted interesting to read that it overwrites the file in that way.  Just an observation but if your users haven't successfully sync'd for any preiod of time you are going to hit a number of sync issues when you resolve the issue so you might need to formulate a battle plan for the users so they are prepared.

Rob-CTL Okay, thanks for the tips, Will test it out today, and see how it goes, will update here later. 

Update.

Tested out what happens if you fully re-install OneDrive client, apply the registry file once more for safe measure.

We initiated this scenario - 

1) Pause Sync for 2 hours.
2) Edit any document on local computer in the synced folder (do not enable sync back on, to simulate pending changes)

3) Uninstall 

4) Wipe OneDrive from Appdata/Local/Microsoft/OneDrive and from registry HKEY_CURRENT_USER/Software/Microsoft/OneDrive

5) Reboot the PC.

6) Run the install of any version of the new OneDrive

7) Run the registry file, that enables preview.

8) Sync all the files.

What happened further - Files, that were mismatched, e.g., edited but not synced previously, had the red X circle on them (sync error), when opening the document, the second it was opened, it overwrites the exact document in cloud completely. Thus rendering any edits in cloud directly discarded whilst the Sync was not working. 

So in a scenario, when 10 people have edited the same document locally from OneDrive synced folder. All of them had issues with Sync afterward, a reinstall would not merge all the 11 versions (including the original), it would overwrite with a version from the person that performs the last sucessfull Sync. 

Therefore Reinstalling OneDrive is no-go scenario. 

Going to atempt to change OneDrive version via registry on a user account when they Sync is actually broken, since I cannot replicate the sync issue on any other computer.

Deleted I see your problem there.  You are correct in the old days with the Groove client if you disconnected a SP library and reconnected it would generally create a new folder on the local PC and sync into there.  Any documents that hadn't sync'd before you broke the initial connection wouldn't get sync'd back.  With the new client you can point OneDrive to use the same folder that was used in the previous sync and it "should" sync everything which means any docs that were only on the local PC would get sync'd back.  Now I must stress I've not tested this so I don't know how reliably this will work so if you were to go down this route I'd do some testing first with test user.

Rob-CTL I really do not want to do that, because I am worried that all the unsynced changes made by the users, that have not uploaded to the Sharepoint, will disappear and everything will be lost. 

E.g., let's say each user has 20 files pending upload to cloud. If I reinstall OneDrive completely, they don't get uploaded. Do they?

So a reinstall might be a no-go.

Curious thing though, I've set up the same sync with a global admin account, and I see files being downloaded as I write this. Going to try with a user account when possible.

Deleted I've not seen this issue.  Have you tried removing OneDrive and re-installing from the link within your Office 365 tenant (https://portal.office.com/OLS/MySoftware.aspx).

Been having a weird bug happen to a whole tenant, that I'm unable to replicate. Initially installed the 17.3.6720.1207 version, and everything was working fine, co-authoring worked, sync was actually happening, as opposed to the old OneDrive for Business. 

However, it auto updated to 17.3.6743.1212 and suddenly everyone in the tenant is running into issues, where there are ~ 700 files ready to be updated / downloaded, but the progess is halting at 0KB/s. After OneDrive restart, it starts up, jumps to ~ 100kb/s in the first seconds, and then goes down to 0 KB/s again. 

No changes made in the past 7-8 days have been uploaded, nothing works at all. 

Anyone encountering this particular scenario with upload/download stuck at 0 KB/s and no progress being made? 

PKlapwijk just for information, I've been rolling out Business Essentials to a new customer so they don't have Office 2016 latest edition.  The OneDrive app that downloads from Office 365 is version 17.3.6720.1207 but more importantly you still need to apply the reg fix as per the preview otherwise you get the GrvOpen errror.

Rob-CTLI see the same behaviour on my laptop, I`m now running 17.3.6743.1212, that version I did not install myself.
But everything is still running fine.

PKlapwijk well that's interesting, I've just booted up the PC I was having issues with.  In the end, last week I went back to the preview version of OD on this PC.  Anyway, I just noticed the OneDrive icons disappeared from the task bar and when they re-appeared it is now running the latest version so it looks like the preview will auto upgrade to the GA release.