Forum Discussion
OneDrive Client, Files on Demand and Syncing large libraries
Thanks for sharing these insights Dustin, it's interesting to hear how OneDrive performs under these conditions and how it might work even better.
Out of interest, do all your user's sync document libraries, like as an alternative to mapped network drives, when previously on-premise?
Actually no, as I am not a glutton for punishment and I didn't want our Service Desk to plot to murder me. For most people, we've switched to using the browser to navigate the content libraries, and reserved the sync client to workloads that require it (CAD drawings, etc). Interestingly though, this has obviously made mobile access much easier and a lot of our users will be getting in through the iOS OneDrive client.
We haven't seen it yet, but one fear we have that I'm sure will present itself at some point is the fact that you can't granularly control who has the right to sync a library, it's either on or off for the entire document library, so I'm sure we will be fielding helpdesk requests for broken clients that tried to connect to too much data, even though they should have been browser-only users.
As a side note, for anyone interested:
If you have a client that has become over-subscribed, you can recover it and manually remove specific libraries from the sync scope by:
1.) forcefully close the OneDrive client in task manager
2.) navigate to C:\Users\user\AppData\Local\Microsoft\OneDrive\settings\Business1
3.) open the {GUID}.ini file
4.) find the sync target entry that begins with either "libraryScope" or "libraryFolder" and delete it and save the ini file
5.) next, open regedit as the local user and navigate to Computer\HKEY_CURRENT_USER\Software\Microsoft\OneDrive\Accounts\Business1\ScopeIdToMountPointPathCache
6.) locate the REG_SZ entry that corresponds to the sharepoint location that you deleted from the ini file and delete it.
7.) perform a reset on the OneDrive client (onedrive.exe /reset)
This will force OneDrive to re-map all local files in scope, but will ignore the location that was manually removed. It is now safe to delete the orphaned files from the library that was deleted from the ini file and the registry
Thanks, that makes sense.
I think it's amazing the progress the sync client has come from the old days of Groove.exe and the workloads that wouldn't have been feasible before, that can now be done with ease.
Oh yeah, the progress has been spectacular, especially with their aggressive release cadence.