A OneDrive for Business installation fails for users confined to an internal network

Applies to: OneDrive for BusinessSharePoint OnlineSharePoint Server 2013


This article contains information that applies when you use the OneDrive for Business sync client (groove.exe).

Note To determine which OneDrive sync client you're using, see the following Microsoft website:
Assume that you download a setup file for a stand-alone installation of Microsoft Office OneDrive for Business from the following Microsoft Knowledge Base article:

2903984 How to install the OneDrive for Business (formerly SkyDrive Pro) sync client for SharePoint 2013 and SharePoint Online

When you provide the file to users who do not have Internet access, the installation fails.


The stand-alone version of OneDrive for Business is available only as a Click-to-Run installation. The Click-to-Run process streams data from Microsoft servers for product installation and updates.


To provide OneDrive for Business to users who do not have Internet access, or to perform a silent installation of OneDrive, use either of the following methods:
  • License an Office 2013 product that includes OneDrive for Business in an MSI (conventional) installation.
  • Create an installation package by using the Office Deployment Tool for Click-to-Run.
This article discusses how to use the Office Deployment Tool (ODT) for Click-to-Run to provide OneDrive for Business to restricted users or perform a silent installation.

How to use the ODT installation

Create an installation package

  1. Download the ODT for Click-to-Run from the following Microsoft Download Center website, and then click Run:

  2. Save the files (Setup.exe and Configuration.xml) to a local folder. You will access this location from a command line. Therefore, you might want to create a short path. This example uses C:\swsetup\c2r.
  3. Open Configuration.xml file in Notepad.
  4. Replace the contents of the file by using the following:


    <Add SourcePath="C:\swsetup\c2r" OfficeClientEdition="32" >
    <Product ID="GrooveRetail">
    <Language ID="en-us" />

    <Display Level="None" AcceptEULA="TRUE" />
    <Logging Path="%temp%" />

  5. Customize the values of the SourcePath, OfficeClientEdition, and Language ID parameters for your environment. SourcePath must be set to the location of the Setup.exe and Configuration.xml files.
  6. Open a Command Prompt window as an administrator.
  7. At the command prompt, move to the local storage folder. For example, run the following command:

    cd \swsetup\c2r 
  8. Run the following command:

    setup /download configuration.xml 
The Setup program uses the information in the Configuration.xml file to locate the OneDrive for Business (“Groove”) files. Then, it creates an Office\Data subdirectory that contains the cab files for the installation. This process takes about 20 minutes to complete over a fast network connection. However, if you share out the folder, you should have to create the installation package only one time.

Test the installation

After you have obtained the cab files, perform a silent installation as a test by running the following command:

setup /configure configuration.xml 
Note The installation can last from 10 minutes to an hour.

Distribute the installation

To distribute the installation, follow these steps:

  1. Copy the folder that you selected in step 2 of the "Create an installation package" procedure to a location that your users can access.
  2. In the new location, open the Configuration.xml file in Notepad.
  3. Edit the value of the SourcePath parameter to match the new folder location.
  4. Have the users run the “setup /configure configuration.xml” command by making whatever changes are appropriate for the location. For example, have users run the following command:

    \\server\share\Setup.exe /configure \\server\share\CustomConfiguration.xml 
To use System Center Configuration Manager to deploy the installation, run the wizard to create a package. When you are prompted, provide the command from step 4.

For more information about the Office Deployment Tool for Click-to-Run, see the following Office 365 TechNet topic: