![onedrive sync client for sharepoint onedrive sync client for sharepoint](https://sharepointmaven.com/wp-content/uploads/2017/05/newonedrivesyncclient3.png)
“OneDrive – Personal” was my consumer, or personal OneDrive, “OneDrive – UnlimitedViz” was my OneDrive for Business storage connected to my UnlimitedViz tenant, and “SharePoint” contained all my SharePoint synced libraries.
ONEDRIVE SYNC CLIENT FOR SHAREPOINT WINDOWS
In the same scenario as above, syncing a personal OneDrive, and a OneDrive for Business with SharePoint libraries from a single Office 365 tenant, I previously wound up with three root nodes in the Windows File Explorer. The user interface insistencies extended to the File explorer integration as well. While we still have more than “One” drive, it’s much more understandable and usable. The icon styles are also now more consistent, and as an added bonus, they always line up at the top of the system tray, which is a nice touch. Hovering over the icon will identify the tenant in question. If two tenants are being used, as in the image below, there will be two blue icons, one for each tenant. The white icon represents the personal account, and the blue icon includes the OneDrive for business as well as all SharePoint libraries being synced. Now the same scenario will show two icons – one white, one blue. If I were interacting with two different Office 365 tenants as I do today, I would have five icons for everything, and while I can certainly cope with it, the inconsistencies made it rather confusing for the end user.Īdding SharePoint libraries to the modern client reduces this complexity. The white cloud represented the sync process for my personal OneDrive, the blue cloud with the bright white border represented my OneDrive for Business, and the blue cloud with the slightly dimmer white outline (really – look at the picture) represented all the SharePoint libraries that I was synchronizing, including Group OneDrives. System Tray InconsistenciesĪfter the rollout of the original NGSC, after connecting my personal OneDrive, my OneDrive for Business, and SharePoint libraries, I would wind up with three OneDrive icons in my system tray. Apart from the technical limitations of the old sync client (no more than 5,000 items per library, no more than 20,000 items across all libraries), adding SharePoint libraries to the new sync client greatly reduces confusion for end users and complexity for administrators. Now add to it the fact that Group libraries were referred to as the Group OneDrive, and it was quite confusing for end users. We had this odd situation in where you would sync OneDrive for Business with the OneDrive Sync client, and all your SharePoint libraries with the OneDrive for Business sync client. Any library contained in an Office 365 Group or a SharePoint site was therefore excluded and resulted in users needing to run a mix of old and new client. Obviously, the biggest disappointment with the original NGSC was the fact that while it added OneDrive for Business repositories in addition to OneDrive personal stores, it was unable to sync SharePoint libraries. With the general availability of the new client today, it seemed like a good time to circle back and see how many of my original criticisms have been addressed.
ONEDRIVE SYNC CLIENT FOR SHAREPOINT WINDOWS 10
You can download it from the OneDrive site, or, if you use Windows 10 and are frequently updating, you’ll get it automatically. The good news is that this new version of the NGSC is now generally available. With SharePoint libraries forming the backbone of all document storage in Office 365, including Office 365 Groups, this shortcoming was particularly glaring. I’ve been running the preview ever since. This version of the client addresses the principal shortcoming of its predecessor – namely that it didn’t synchronize SharePoint libraries. In September, at Microsoft’s Ignite event in Atlanta, Reuben Krippner announced the public preview of a new sync client (as I like to call it, the Next Next Generation Sync Client”. True to their word, it seemed that every time I presented that session, I had to modify the slides in one way or another, as another feature was added, bug was squished, or idiosyncrasy clarified. In that post and session, it is pointed out that the NGSC still had some work to do, and that it would get done.
![onedrive sync client for sharepoint onedrive sync client for sharepoint](https://i0.wp.com/uviwebstorage.blob.core.windows.net/whitepagesstore/2017/01/012717_1952_Enablingthe3.png)
![onedrive sync client for sharepoint onedrive sync client for sharepoint](http://s36505.pcdn.co/wp-content/uploads/2016/09/onedrive-sync-select-files.png)
I then turned that post into a speaking session (Changing the title slightly to OneDrive, TwoDrive, White Drive, BlueDrive), and that session has been presented at many events over the past year. A little over a year ago I wrote a post entitled “ OneDrive, TwoDrive, ThreeDrive” in which I took a slightly cheeky look of what has become known as the “Next Generation Sync Client” (NGSC) for OneDrive, and its many idiosyncrasies.