Forum Discussion
Issues with NGSC Takeover Process
MicrosoftHi Andy,
Thanks for the detailed write up. Let's jump in here
For case #1, can you confirm that your version of Office was one of these versions or higher. Since you were hitting "Sync"
|
Office 365 ProPlus |
16.0.7167.2* |
|
Office 2016 MSI |
16.0.4432.1* |
|
Office 2013 MSI/C2R |
15.0.4859.1* |
For case #2, let's investigate that. Expected behavior is for all libraries to be taken over by the OneDrive sync client. We expect /takeover to be a one time event. Making you manaully disconnect libraries first defeats the whole purpose :) could you please right click on the blue cloud icon in your Windows task tray (bottom right corner) and click report a problem. If you want to link to your helpful sway and submit, we'll investigate.
Thanks,
Pat
Hi Pat. Thanks for the reply. Yes, my NGSC version is current and my Office C2R version is greater than the minimum required version. I am not going to pursue the Report a Problem route for two reason. 1) In my experience "Report a Problem" does not get to the level of troubleshooting that I usually hope for. In my experience it usually results in a series of generic How-To emails. If I were to pursue a ticket I would use either a submission through Office 365 or via my MS Partner benefit. But, more important, is 2) as I stated in my original post. I had already opened a ticket with Office 365 support, but I cancelled it because I ran out of clean test cases. I eventually ended up manually interacting with each migration to nudge it along. My post was to explain my experience so others can benefit if appropriate, but I've moved on and have completed our Groove to NGSC migrations for all client endpoints. It's a moot point for me now. Thanks.
- Patricia Hendricks Balik
Hi Andy,
We actually discovered a really good bug thanks to you! In the case of running /takeover in the case where there are multiple libraries syncing with Groove that all resite in the same site, takeover was only taking over one of those libraries at a time.
We have a fix in progress. In the meantime, your work around will need to be to go to each of the remaining sites on the web client and hit "Sync" for each site, or run /takeover multiple times to get all the sites (not great, we know). Thanks for reporting this and we'll make sure we get this fixed as soon as we can
Hi Particia,
As of today takeover approach still produces Andy's #1 problem at our client. Can we have an update on the state of this issue?We're having similar issues here. I am both frustrated and unsurprised that something as simple as "transferring multiple libraries from the same site doesn't work at all" made it all the way through to production, and required someone posting here for you to acknowledge a bug. If this behaviour wasn't tested, what was?
Is the sync client updated yet for this behaviour? We are currently experiencing the same kind of issues using the most recent NGSC version. Takeover command does not seem ready yet to deploy to all users. A premier ticket has been raised.
I am glad that my writeup helped the process of discovering this /takeover bug. Thinking about this fact I am surprised that this bug made it this far. Here is why.
According to your reply, the bug applies to sites with multiple libraries being sync'd. In my world that means every site instance. The only time that it would be possible in any of my worlds to have a single library in a site is if I stopped at the default "Documents" library, but given the limitations of the former Groove.exe client, that was nearly impossible. The Groove.exe client limited sync to 5K items per sync instance. I've always argued that, in most enterprise environments, 5K was minuscule. The result was that we always had to break up libraries into sometimes artificial groupings to satisfy the limitations of the Groove sync engine. So, in my use cases, it was rare to end up with a single library per site.
I am just surprised that my experience was not the norm. I'm assuming that you have to telemetry to know and that's what leads to my surprise that this wasn't caught earlier.
Anyway, I am glad to hear that it's been addressed and will be fixed in future sync client releases.
Andy
