This article is for Office 365 admins whose users are running the previous OneDrive for Business sync client (Groove.exe) on Windows computers and who want to upgrade to the new OneDrive sync client (OneDrive.exe) to sync files in OneDrive for Business and SharePoint Online.
If you're not an IT admin, see Sync files with the OneDrive sync client in Windows to learn how to begin syncing files using the new OneDrive sync client.
The new OneDrive sync client for Windows now supports syncing IRM-protected SharePoint document libraries and OneDrive locations. To create a seamless IRM sync experience for your end users, deploy the latest Rights Management Service (RMS) client to your users' computers.
If your organization never used the previous OneDrive for Business sync client, or had fewer than 250 licensed Office 365 users in June 2016, your users must use the new OneDrive sync client to sync OneDrive for Business and SharePoint Online files.
The new OneDrive sync client supports Windows 10, Windows 8.1, Windows 8, and Windows 7. It doesn't yet support syncing on-premises instances of OneDrive for Business or SharePoint Server (when your organization doesn't subscribe to an Office 365 business plan).
If you're ready now, download the latest version of the new OneDrive sync client that's fully released to production. To learn about other versions that are rolling out to different rings, see New OneDrive sync client release notes.
When users who are syncing files with the previous OneDrive for Business sync client (Groove.exe) sign in to the new OneDrive sync client (OneDrive.exe), the following things happen:
If the new OneDrive sync client can take over syncing a library, the previous sync client stops syncing it and the new OneDrive sync client takes over syncing it without re-downloading the content. If the new OneDrive sync client can't sync the library, the previous sync client continues to sync it. If a library requires checkout or has required columns or metadata, it will be synced read-only.
The previous sync client stops running and removes itself from automatic startup, unless it’s still syncing libraries that the new OneDrive sync client can't sync.
When SharePoint Online libraries begin syncing with the new OneDrive sync client, the folder hierarchy that appears in File Explorer may be simplified.
The following library types are not yet supported by the new OneDrive sync client, and will not transition from the previous sync client:
On-premises instances of OneDrive for Business and SharePoint Server (when your organization doesn't subscribe to an Office 365 business plan).
SharePoint Online libraries that people from other organizations shared that your users are syncing with the previous sync client.
Make sure users have the following versions of Office or higher installed. For info about deploying Office, see Choose how to deploy Office 365 ProPlus. Make sure you don't install the previous OneDrive for Business sync client. For info, see Changes to the previous OneDrive sync client (Groove.exe) in Office 2016 Click-to-Run.
Office 365 ProPlus
Office 2016 MSI
Office 2013 MSI/C2R
Make sure users have version 17.3.6743.1212 or higher of the new OneDrive sync client installed. For info about deploying the new OneDrive sync client, see Deploy the new OneDrive sync client in an enterprise environment.
If any users have Office 2010 installed, we strongly recommend removing the SharePoint Workspace component. If users previously set up SharePoint Workspace (even if they're no longer using it), it will cause problems syncing team sites. Before starting OneDrive Setup, either uninstall Office 2010 or modify the installation. To do this by running Setup, first create the following XML file.
<Configuration Product="ProPlus"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" NoCancel="yes" AcceptEula="yes" /> <Logging Type="standard" Path="C:\Windows\temp\" Template="MicrosoftSharePointWorkspaceSetup(*).txt" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <OptionState Id="GrooveFiles" State="absent" Children="force" /> </Configuration>
Then run Setup:
Setup.exe /modify ProPlus /config RemoveSharepointDesigner.xml
In the SharePoint admin center, set SharePoint to sync with the new sync client. If the options aren't available, the new OneDrive sync client is already set up to sync OneDrive for Business and SharePoint Online files.
If you're running Windows 10, you can use silent account configuration to sign in users. For info, see (Preview) Silently configure OneDrive using Windows 10 or domain credentials.
Run the takeover command
If you don't run the takeover command, users transition to the new sync client by:
Launching OneDrive Setup (first-time users of the new OneDrive sync client).
Setting up additional libraries (existing users of the new OneDrive sync client).
To automatically transition file syncing without the need for user interaction, you can run the takeover command. Use a tool such as System Center Configuration Manager (SCCM) and run the following command for each user on a PC:
Make sure to run the command in a user context, rather than as admin, or the user will see a "OneDrive.exe cannot be run with Admin privileges" error.
To affect all users on computer, configure the command to run on every user account. This will ensure that it's executed for any user who signs in.
Block the previous sync client from syncing
To prevent users from using the previous OneDrive for Business sync client to sync their OneDrive for Business and SharePoint Online files, run the following command in Microsoft PowerShell:
Set-SPOTenantSyncClientRestriction [-GrooveBlockOption <String> “OptOut”|”HardOptIn”|”SoftOptIn”]
For more information, see Get-SPOTenantSyncClientRestriction. For information about using PowerShell, see Introduction to the SharePoint Online Management Shell.