I've been using the new sync client for ~1 year and while it's magnitudes better, it's still not perfect. Converting a Doc Library into a shared network drive seems counterintuitive / working against the tech.Unless each user is licensed for Sharepoint, this may be outside of terms of use/licensing (piggybacking multiple users on top of a single Sharepoint user).What your goal by doing this - a form of redundancy/backup? Do people ever access via Sharepoint directly? I've heard of others considering this, but never heard of any widely successful implementations. So, I know there are gotcha's here, I just can't think of them. I know there are third party tools available to do this, but I'm on a tight budget (read: no budget) and if the new sync client is functional I don't see why we would need/want a third party tool. (It would not be practical to configure OneDrive for every user on every computer they'd need it on, thus the need for a central file server) We then map this folder as a network drive for User A, who is not technical, may need to login to multiple computers in a day, and does not have an Office 365 license. Here's an example: We have a document library labeled "Quality Department" in Sharepoint which is synced locally via OneDrive to a file server (using a dedicated O365 service account).That local OneDrive folder is in our DFS Namespace. I understand that previously, OneDrive for Business's limitations made this impractical - the file limits, bugs, and fragile syncing would have been a disaster.īut what about the new sync client? Is this now a consideration or a possibility? Like many others, we're interested in syncing our DFS shares on our file server with our Sharepoint Online libraries. I've searched but many of the related topics deal with the old One Drive for Business sync client, not the new one. I apologize if this is posted somewhere else.