Forum Discussion
Issues with NGSC Takeover Process
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
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