Forum Discussion
GA OneDrive for Business Next Gen Client version number
Hello,
Earlier this week Microsft announced the GA of OD4B Next Gen client update to support sync of SharePoint libraries (https://blogs.office.com/2017/01/24/onedrive-brings-new-file-collaboration-and-management-features-to-the-enterprise/).
Within release notes (https://support.office.com/en-us/article/New-OneDrive-sync-client-release-notes-845dcf18-f921-435e-bf28-4e24b95e5fc0?ui=en-US&rs=en-US&ad=US) it is said that GA version is 17.3.6743.1212 but it was also this built number for last preview client in December and I founded some informations about a new built number for GA : 17.3.6760.0105 without ability to download it.
Reading some articles it seems that I am not the only one confusing with GA built number. Can someone within Microsoft (perphaps Stephen Rose) could tell the community what exact built number is for this GA of OD4B NextGen clent supporting Sharepoint sync and activity center and provide download link?
Also within deployment information it is always said that we need to add registry key to enable Sharepoint sync. In the past I have read that this registry addition will not be anymore necessary after GA.It it or not the case? Perhaps documentation have not been updated yet.
Thanks for help and clarifications.
Vincent
12 Replies
- GA is 17.3.6743.1212. This is reflected in the documentation.
- Please check out the documentation "Enable users to sync SharePoint files with the new OneDrive sync client" for enabling this feature. 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
Stephen Rose wrote:- GA is 17.3.6743.1212. This is reflected in the documentation.
- Please check out the documentation "Enable users to sync SharePoint files with the new OneDrive sync client" for enabling this feature. 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
Sorry to interrupt but your linked article still talks about the Preview Client and also that you need the Registry Keys to make it work with SharePoint document libraries.
This is not necessary anymore. That article is obsolete and neither contains a version number nor even a date! It only talks about "the new client" but doesn't specify it.
The release notes of OneDrive are here:
A manual about the transition from the old client (Groove) to the new one is here and it also includes the minimum version numbers for Office.
Basically you bring your computer up to date (Windows, Office), check the version numbers, and send the NGSC the following command:
%localappdata%\Microsoft\OneDrive\OneDrive.exe /takeover
Now the new client moves the synchronized libraries from Groove and takes over. If all went well it also removes Groove from Autostart.
I have done this with a few machines in our office already and it worked.
Basically you bring your computer up to date (Windows, Office), check the version numbers, and send the NGSC the following command:
%localappdata%\Microsoft\OneDrive\OneDrive.exe /takeover
Now the new client moves the synchronized libraries from Groove and takes over. If all went well it also removes Groove from Autostart.
I think what everyone is wondering, will this ever be completely automated and silent to take over without the need for running this command?
Thanks Stephen Rose for reply.
So nothing change since last preview version in December even version built number et deployement using registry key?
I have read about a GA version with built number 17.3.6760.0105 but found no where to download it.
Thanks to confirm because as said Bruce Piper it will change deployement consideration
Regards
Stephen Rose, can you confirm that the manually adding the registry key is still required to enable SharePoint libraries to be synched as the posted documentation mentions? I thought that a feature of GA was removing this requirement and enabling automatic takeover from Groove. If not, that changes the deployment considerations greatly.
