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.
I'm gonna try giving the user customize permissions on the SP site to see if that allows the .jar files to sync.
Why are they storing jar files in ODFB? Seems odd to me, but I assume there's a rational explanation.
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...
Alan_McFarlane wrote: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...
Yeah that sounds less than ideal :-)
I've had some issues with the preview client this week. Work I did on my main computer hasn't synced to the library apparently. I think the client is stuck in "processing" status, but now I'm in another country so it's a little difficult to troubleshoot :-/