Forum Discussion
My experience with the new OneDrive Team Site Sync
The changeover was reasonably easy. Having to stop sync and then re-sync everything was a little annoying but the new client build seems to sync faster than the legacy client, so it's bearable.
I've had the new build crash a few times when adding a new document library to sync, but other than that it's been stable.
Interestingly, the old groove.exe client seems to have been ignoring file type restrictions that were set on the libraries. The new client respects them, so all of a sudden a bunch of Zip files in our group library got flagged.
I also noted that reinstalling/repairing Office on your computer reverts to the non-preview build and lost the ability to sync libraries, so I had to repeat the preview install + reg key steps.
- Alan_McFarlaneOct 07, 2016Iron ContributorI've tried it in one new user. They had .jar files. They wouldn't sync. The new Activity window was going kinda psychadelic. Not pleasant. Flashing between a red warning about that and the normal blue progress reporting of the other (100s) of files upload progress. (BTW I was accessing the PC remotely.)
I'm gonna try giving the user customize permissions on the SP site to see if that allows the .jar files to sync.- Paul CunninghamOct 07, 2016Iron Contributor
Why are they storing jar files in ODFB? Seems odd to me, but I assume there's a rational explanation.
- Alan_McFarlaneOct 10, 2016Iron Contributor
So, the user has a business app written in Java where the suggested backup solution is just to copy the whole folder. So they thought, just plonk it in my team's site...
Adding the customize perm has let the .jar files sync. The consequences of that to the SharePoint site I don't know...
- Randy NieraethOct 04, 2016Iron Contributor
Im having mixed results with the new client and reg key.
Adding multiple SharePoint Doc Libraries is resulting on OneDrive crashes on some clients.
One client which worked well over days, keeps on crashing after startup.
It had 5 shared OneDrive for Business folders in sync. Once deleted it works well again.
My experience is mixed based upon this.
I know it will be a great addition but right now im not pushing it out in production environments.
Anyone having these same experiences, or getting luck of repairing the issue when multiple SharePoint Doc Libraries are synced?