Forum Discussion
Issues with NGSC Takeover Process
I am surprised that there were no replies on this thread. I'm not sure whether to conclude that no one else is experiencing this issue (meaning specific to me...or caused by me) or whether not enough people are using either of the takeover methods. I have reproduced this across multiple tenants, library structures and OS variants so I'm having a hard time believing that it's just me. The other possibility that I was thinking about is that, since migration is a one time deal, that it's just not that important in the long run. Another solution is to just Stop Sync'ing all Groove libraries and then resync them on the NGSC side. My hope for the takeover process was to avoid the unnecessary download. We all know the story. Remote users, low bandwidth users, etc, + multiple GB libraries equals pain. Maybe it's Groove's one last sucker punch to me!
I created a Sway to document my experience.
https://sway.com/EV9tClm5EIqvhHas
I'd still love to know if anyone else experiences the takeover process as documented.
I'll add a few mentions for good measure: Stephen Rose, StephenRice, Randy Wong
Sorry for the shotgun approach. That's the danger of being in an AMA.
Hi Andy,
I havent faced the first 2 parts of the issues and I used the reg edit, not the takeover, however Im facing the issue number 3 myself.
What is also counter to documented behavior is that, when a takeover does occur, I see all documents in the library scrolling through the NGSC Notification Center dialog being shown as downloading. I haven't actually sniffed the wire to watch the transfer occur, but it certainly looks like it's downloading the entire library again which is counter to the documented statement that files won't be re-downloaded.
All libraries in my company re-download almost on a daily basis. I have been following up with MS on the issue for 3 weeks almost but they still havent been able to figure it out. It seemed like we were the only one facing the issue until i read your post. I have shared all evidence of the issue to them and they told me to wait till the next update of NGSC but Im skeptical since they havent figured out whats wrong.
For us, we recently moved to OneDrive so we never had to switch from Groove, so this isnt a transition issue.
