Forum Discussion
My experience with the new OneDrive Team Site Sync
Can anyone confirm that you can only sync SharePoint libraries with the new client if you are using the new sharepoint library experience?
When I click on the Sync button in the classic library, the NGSC will open, but ask me to log in to sync. When I enter my credentials, it will say that I am already logged in with that account.
If I click on the Sync button in a SharePoint library with the new experience enabled, it appears to work as designed, where the NGSC will pop up and let me choose which folders to sync.
Is this working as intended? Are we going to be forced to use the new library experience (which doesn't allow users to manage their library alerts after they've been created) to sync using OneDrive?
Michael
So yes, it looks like you are getting forced into the new library experience.
Don't forget the possible limitations:
I Quote:"
Several features are in the process of being rolled out and may not be available globally yet:
- Support for shared folders
- Support for Mac
- Automatic sync takeover from groove.exe
- Read-only sync of files from read-only libraries, libraries that require check out, or libraries with required columns or metadata"
- Michael BairdOct 06, 2016Brass Contributor
I just tested with a couple end users. Both of which were unable to sync using the new client while using IE - no matter which library experience was activated, or after disabling the activeX control in IE. The only working solution was to sync the library in Firefox (library experience did not matter in this case).
I believe there is fine print in the troubleshooting section for this beta version, explaining this may be the case in Windows 7 & IE...
- DeletedNov 02, 2016
Yep...
NOTE: There is a known issue in Internet Explorer with Windows 7 and SharePoint libraries using the Classic UI that may prevent your libraries from syncing. If you have tried both of the above workarounds and are still having trouble, please try a different browser such as Edge, Chrome, or Firefox while this issue is being investigated