Forum Discussion
Unable to install NGSC
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.
In a new machine, to be clear:
- OneDrive comes with Windows 10 and after installation it should automatically upgrade itself to the latest version (i.e. NGSC).
- Groove comes with Office 2016. In Office 2016 C2R you cannot uninstall it, but you can terminate it and remove the shortcut from shell:startup.
- In order to automatically start OneDrive sync (and not Groove sync) when you press the Sync button in SharePoint you should set the correct default in the SharePoint Admin Center.
Where, exactly, do you have problems?
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-client-4100df3a-0c96-464f-b0a8-c20de34da6fa?ui=en-US&rs=en-US&ad=US&fromAR=1. 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.
In my experience, I found the following:
- If OneDrive is already installed (as it always is in Windows 10...), it is much better to leave it alone. It will update automatically and seamlessy. I've never had much luck trying to force an update by reinstalling (as it appears you are trying to do...). Of course if it is not already installed (so this does not apply to Windows 10...) then you need to install it in first place.
- 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...
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:
https://support.office.com/en-us/article/Enable-users-to-sync-SharePoint-files-with-the-new-OneDrive-sync-client-22e1f635-fb89-49e0-a176-edab26f69614?ui=en-US&rs=en-US&ad=US
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.)
