Forum Discussion
OneDrive Client, Files on Demand and Syncing large libraries
dustintadam thanks for sharing your findings. We have multiple customers struggling with OneDrive and files on Demand. We see the same performance CPU peaks when 'syncing' large SPO library's.
How to continue, that's the question....
Customers are thinking about leaving the Onedrive SPO sync, and start using the old network connection feature. Which also comes with other issue's. Like filenames, and session time-outs. Last resort would be to go browser only. But this is a huge change for users, well for most of them.
Martijn Steffens If you are considering the drive mapping approach http://www.thinkscape.com/Map-Network-Drives-To-Office-365-OneDrive/. Zee Drive maps network drives to OneDrive for Business and SharePoint Online. Zee Drive will keep users authenticated and it also provides a number of useful productivity features off the File Explorer context menu.
Myles
I can understand why you'd have customers thinking twice about their OneDrive deployments. In our case, we were... fortunate? in learning in advance about the pitfalls and spent an inordinate amount of time in planning before making a transition. As powerful as the technologies are, they are still plagued with a large number of upper limits that serve to significantly raise the bar to entry compared with other cloud storage platforms:
List view thresholds, 50,000 ACL limit per library, API throttling, 1000 clients per library, Sync limits, etc. Not only did we have to account for all these limits and understand them in great detail, we had to translate our on-premise content and find ways of making it fit inside Sharepoint.
Not all organizations understand these limits, or are willing to expend the energy that we were to move their content in such a way as to make it work. Case in point, we had a custom Azure web application developed that would propagate and manage a very granular permissions model onto our content in SharePoint so that we could both reduce our risk profile by restricting what content could be shared externally and have a mechanism to reduce the load on a sync client. It was an elegant solution to a complicated problem, but again... the bar to entry was high.
So far for us, the "answer" has been to place an exceptionally heavy emphasis on permissions that grants us the administrative control needed to manage the limits.
