“Sorry the install hasn't worked for you Andy. I would suggest running Windows update first then try the install - if this fails then please contact our support team. Hope this works for you! Thanks again!”
“Thanks for the feedback - more to come in this app later this year - stay tuned!”
“Hi Petr, the old sync client (groove.exe) will remain in the setup until groove.exe is no longer needed. Once we get shared folder and team site sync for both cloud and on-prem into the new client then groove.exe will be included but doesn't have to be used. As far as the sync button in the web client you'll have the option to default the sync client that suits your needs - this feature will roll out during April. Thanks!”
“Hi Brian, thanks for the feedback. I can confirm that the work we are doing on SharePoint sync also includes Shared Folder sync - exactly the scenario you outline above. Reiterating dates: Q3 TAP, Q4 GA. We'll have more prescriptive dates for you in the coming months - stay tuned.”
“Hey Paul, definitely respect your position on this.
Let me respectfully challenge that position. Assuming that we did light up the feature that you can only sync SP doc libs that you have write access to, would that be an acceptable experience? As we've discussed this with customers they feel that doesn't meet the bar. The concern is that the user may feel that they will be able to sync folders they have access to (regardless of what permission level they have) and be very disappointed if files or folders are "missing".
We also have to factor in the aspect of someone who has write access to a folder within a site they don't have access to at the top level - all of these things are not trivial exercises to work through.
Believe me, we've wrestled with the right approach and talked to lots of customers and partners about a minimum viable product and this has informed our approach here.
Finally, I would add that no other vendor in the market has a sync client that syncs both their individual file store as well as SharePoint - we will be the first and we want to get it right.
Again, I completely respect your eagerness to get this delivered and we want to get it to you asap - as soon as the dates for the TAP are announced I would love to have you participate and provide feedback.”
“Justin, appreciate the feedback. I want to address some of your comments and concerns.
Gartner's assessment is actually on a different cadence than Forrester. We are currently going through the exhaustive review process with Gartner for the next MQ and feel positive about our submission. The new MQ gets published later in the year and we're excited to see where we land! On the vision front we have a lot to say about this in the Future of SharePoint event on May 4th (https://vts.inxpo.com/Launch/QReg.htm?ShowKey=30784&AffiliateData=ODBAprilBlog) - I encourage you to tune in for that where we'll unveil our vision for SharePoint ad OneDrive and some significant product innovations.
On the unified sync engine we heard loud and clear about the need for SharePoint AND ODB sync at our customer event Ignite in May 2015. Our commitment we made there was to ship rock-solid, performant sync for ODB which we have done and continue to invest in with this update. Based on the Ignite feedback we've committed to SharePoint sync. The reason for the timelines with SharePoint sync is the security model, we need to teach the client to do read-only sync because of the potential for people to have read-only access to doc libraries and want to sync files for viewing offline. This is not a trivial exercise to get right and it's clear that the old client did not hit the mark in that area. Coupled with the fact that read-only sync has implications for the Office and Windows experience - we need to get that right across every way that users work with files on SharePoint. rest assured we're working as quickly as possible to bring this new capability to the client and we'll keep you informed along the way.
Finally, placeholders is an incredibly emotive discussion. We delivered this with Windows 8.1 and only for the consumer service. Based on overwhelming feedback from users we removed it from the client for all other OS. Obviously, the users that liked placeholders and had it taken away are upset and we respect that and hear the feedback loud and clear. The decision was a difficult one to take but one that we felt was right to deliver the quality of user experience needed. Our primary objective with the new sync client has been to deliver reliable and performant sync for all consumer and business users before we look at other desktop integration scenarios. We’re absolutely committed to delivering fast, simple and consistent experiences on the desktop with OneDrive where a user can choose what they sync on their device as well as the ability to browse, search and access all their OneDrive files from their device without having to sync them. As plans mature we'll absolutely disclose those as soon as possible.
“Thanks Lou, we glad you like the news!”
“Thanks for the feedback! We'll have more news on the Windows apps soon - stay tuned!”
“Thanks for the feedback. It should be included in the O2016 payload but still requires a registry key to enable the connection to OneDrive for Business. This need for a registry key will be removed in early Q2 2016. Stay tuned!”
“Jan, thanks for the feedback and we're working hard on completing some fit and finish on the new sync client. Windows 8.1 support will be added by the end of March which should complete the OS picture. From there in early Q2 2016 we'll remove the need for a registry key to enable the connection to OneDrive for Business - this will make the client a far more self-service experience for end-users vs the IT-led deployment model today. We're also introducing a pause sync option for end-users.
This should mean that the user experience for setup is simple and combined with the reliability we're now seeing with the new sync client then sync should be where it needs to be.
Have you tried the new client? I trust that once set up you are seeing significant improvements in performance and reliability. Please contact me directly if this is not your experience - we always want to hear feedback on where we can improve.
If SharePoint doc library sync is required then the good news is that we have it committed on the roadmap and the engineering planning is almost complete - we'll be able to provide pre-release and GA timeframes for you soon. Thanks again!”