Forum Discussion
Issues with NGSC Takeover Process
I'm checking to see if anyone else has had issues with the OneDrive.exe /takeover process. Specifically, I have not had the documented behavior of SharePoint (groove.exe) to [Company Name] (OneDrive....
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.
Patricia Hendricks BalikMicrosoft
Hi 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 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.
Hi ABaerst - thanks for the comprehensive share on this topic. To date, my takeover testing has been with the reg key approach, but for mainstream adoption I was considering the /takeover switch to put some control to the end user. The reg key approach was not without issues either, but most of them were during the "preview" phase of the program, so you expect some issues. I assume you are now on the latest bits - .1212?
Anyway, I will be performing some of my own testing going forward, and will revert if I am seeing similar.
Thanks
Cliff
- Stephen Rose
Sorry Andy,
I'll pass this onto our engineers and have them review and answer.
