Forum Discussion
Solved
Which OneDrive client version included in which Office update channel?
We are trying to solve one hard riddle. Which OneDrive client version is included in which Office update channel by default? There is a Insider Fast, Insider Slow, Current Channel, First Release ...
The Next Generation Sync Client comes with his own Update mechnism, has nothing to do with Windows Update or WSUS. Each day once the client is looking, if Microsoft has released and appoved for this channel (yes, there are more) a new version. So it could be, that one Tenant A has another version then Tenant B.
Why:
If Microsoft has done several new things on Office 365 Servers, it could be that they need also a new NGSC version to sync data between the cloud and the devices. Then Microsoft will publish...04/04/17
We have today the NGSC version 17.3.6798.0207 (and wherever you download it for Windows 7, this is the latest Released version.But If You are an Windows 10 Insider and have the Creators Update installed, your NGSC Version is 17.3.6816.0313. You may look here
The NGSC is installed on each new Windows 10 device (with an old version). and you do not have to update it by yourself. It will be updatet automatically, even if you are not connected to OneDrive Personal NOR OneDrive for Business NOR Groups, Team Sites, or Teams.
You may install it manually to:
Windows Vista SP2, Windows 7, Windows 8.x, MAC OSX, Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016
So if you manually download an install it, (although via GPO), it's a good idea to reboot your device.More ionformation you will find here
Hans Brender, MVP Office Servers and Services
Whatever version of OneDrive is initially installed by Office 2016 C2R (all channels) or by Windows 10 (all versions), it will update automatically itself to the latest version (i.e. the latest NGSC version), independently from Office updates and from Windows updates. Hence, leave it alone... :-)
Groove, instead, is installed by Office and is updated together with Office updates. Anyway, don't use it and go with NGSC... :-)
I would really like. Our customer really would like.
But they are sometimes using SharePoint Server which is not supported by OneDrive Next Generation Client. Some of them also using both. So need basically both clients. And old steps how to install the older client with a new one does not work for some update channels because they are not anymore on 2013 version of Office which will be outside supported in Office 365 ProPlus, but they are on 2016 versions. And with patching with SCCM and strict AppLocker rules it can be hard to maintain and test all changes.
The worst thing here is that user can search for OneDrive in Start menu and the old client starts up and take sync even a new version is syncing. The takeover process to new one is not also so easy without SCCM by takeover switch.
Hi Petr.
Sorry but I think I don't understand fully your problem...
You are asking: "Which OneDrive client version is included in which Office update channel?".
Now, to summarize, we have the following:
- Onedrive.exe (NGSC). Whatever version is initially installed, it will soon update automatically and independently to the latest version. Hence it should not be a problem.
- Groove.exe (old client). It comes initially in the same version and build of the Office 2016 C2R it is bundled together (monolithically). Every Office 2016 C2R subsequent update is monolithic too, and updates Groove to the same version and build of the whole package.
Does this answer to your question?
Hi Salvatore, I do understand Petr.
There should be a page, where any customer can see what version of what client is in given branch. A version number would be best.
If you can fill the build numbers of the OneDrive.exe, this is what Petr is asking for:
ChannelVersionCurrent
OneDrive.exe version build XXX
First Release for Deferred
OneDrive.exe version build YYY
Deferred
Groove.exe
Deferred 2
Groove.exe
- Unfortunately OneDrive.exe is not bound to any C2R channel. It is using its own update logic. You can only prevent to the second wave via GPO, but you have no way to see when the first finished.
