Feb 24 2017 11:04 AM
On a Windows 10 PC with Office 2016, we are not able to install the NGSC. The install begins but then disappears and the Task Bar still shows up the groove version. Does anyone have any tips about how to troubleshoot?
Feb 25 2017 03:25 AM
Hi Dean.
Out of curiosity, why are you trying to install NGSC on a Windows 10 PC?
OneDrive is already part of Windows 10 and it should update itself automatically to the last version...
Feb 25 2017 04:39 AM
That is a very good question. I thought the same, but when we looked at the machine we noticed that it is running Groove.exe. We are trying to get it to the proper configuration.
Feb 25 2017 04:52 AM - edited Feb 25 2017 04:53 AM
In a new machine, to be clear:
Where, exactly, do you have problems?
Feb 25 2017 07:55 AM
My client uses SCCM to manage their computers. He deployed Office 2016 using SCCM, I'm not sure how he got Windows 10 onto the computer (I will find out on Monday). They have not been using O365 very much (just for Mail) and I'm helping them get ODfB activated We are testing out various scenarios, most of their machines are Win 7, Office 2013, but they also have Win 8.1 and 10, not very many with 2016.
I have changed the SPO Admin center settings to use the new sync client.
He showed me that he the groove client and that it was syncing. We have been trying to get that switched to the onedrive.exe without any success. He had some sync errors so we did a repair and those went away.
I'm using https://support.office.com/en-us/article/Transition-from-the-previous-OneDrive-for-Business-sync-cli.... We used SCCM to deploy an Office 2016 update to his laptop to get him to the most recent version. We downloaded the file and when it ran it never gets to the Setup screen to enter his account credentials and choose the folders to sync. It just disappears and the old client (groove) is still in the System Tray.
Grazie in advance for any suggestions you have.
Feb 25 2017 08:25 AM - edited Feb 25 2017 08:26 AM
In my experience, I found the following:
Just my two cents...
Feb 26 2017 10:22 PM
@Salvatore Biscari wrote:The takeover from Groove does not always work well. So, if Groove is already syncing, I would advice to carefully consider the total size of synced files. If it is not very big (compared to the available bandwidth, I mean) I would not force the takeover. Simply stop syncing, delete the local stuff, remove Groove from shell:startup and finally sync fresh with NGSC (pressing the sync button in SharePoint).
Just my two cents...
Everything Salvatore wrote is true!
I only want to add that you have to turn on the setting in SharePoint Online where you enable syncing with the NGSC instead of the old one. See chapter "Set SharePoint to sync with the new OneDrive sync client" at the bottom of:
Then un-sync the libraries, move them out of %userprofile%, and sync them again (the NGSC should be triggered by this).
I specifically said "move" because you should compare the newly synced files with your old version. We had some instances where some files where missing from the SharePoint library even when Groove showed us "all green" and no sync errors! (The problem most likely stemmed from previous sync errors, long filenames, deep directories, or all of the above.)