How to deploy SkyDrive Pro 2013 Client as a stand-alone application


Update: This information is still relevant pre-service pack 1 for Office 2013. Since the service pack release, SkyDrive Pro now has been renamed to OneDrive for Business and the standalone download has been repackaged also.

Update from Microsoft: SkyDrive Pro Stand-alone Client is now available for download:

For some additional licensing information read Hans’s post:

If you’ve worked with the new SharePoint 2013 Server you will have most likely come across the new synchronised storage feature that Microsoft has launched in the ‘My Site’ service application. This new feature is called SkyDrive Pro and is underpinned by the same technologies used to deliver the consumer equivalent cloud service called ‘SkyDrive’.

This synced storage concept is great, although to actually sync your files, currently you need to install Microsoft Office 2013 to access the new SkyDrive Pro client. This new client ships with the Office suite and replaces the SharePoint Workspace 2010 product; which has been noted as ‘discontinued’ in future Office releases although supported until Office 2010 becomes end-of-life.

There is news from the SharePoint Team regarding the release of a stand-alone free download to enable users to install the SkyDrive Pro client without the need to upgrade the whole Office suite. Until then I have a quick workaround to deploy the SkyDrive Pro client to your workstations. This might technically be in breach of the EULA if the computer your deploying SkyDrive Pro to is not already covered under an existing SA agreement or licensed to use Office 2013 appropriately. Until the official download is available from Microsoft; consider this in terms of licensing as if your installing the full Office product for that device.

The Workaround

  1. Copy your Office 2013 media to a network share, and launch the Office Customization Tool (OCT). To launch the OCT you need to run the following command: Setup.exe /admin
  2. Inside the OCT you need to customise the feature installation states to reflect only the SkyDrive Pro 2013, and choose to not install any other options. You may leave all other customisations un-touched.
    See screenshot below:
  3. Now save the customisations to a .MSP file. Click the File menu and choose the save option. Save your MSP file in the directory called “Updates” from within the location where you copied the Office installation media on the network file server.
  4. Now when you run Setup.exe in standard mode, setup will take the customisation file placed in the Updates folder and execute setup based on the options defined in the customisation file.

Additional Notes on using the OCT:

  • For those who are not familiar with the OCT, you must understand that the Setup.exe program can only accept one customisation file. You must not place more than one .MSP file in the Updates folder otherwise your setup might fail or unexpected installation results will occur.
  • If you wish to have multiple customisation files for different Office deployments, store them in a shared folder outside of the Office installation media share. You can then use the switch /adminfile “\\server\share\custom.msp” where you place your path to the customisation file when running Setup.exe.
  • This information is specific to the 32-bit version of Office 2013, the process is similar for the x64 build but you must create a separate customisation file using the x64 Setup.exe program. The customisation files are not cross-architecture compatible.
  • For full documentation on using the OCT and for technical reference to all the options presented in the tool and for supported Setup switches see the TechNet article on OCT –
Rating 4.00 out of 5

7 thoughts on “How to deploy SkyDrive Pro 2013 Client as a stand-alone application”

  1. Pingback: Sharepoint 2013: Skydrive Pro / SharePoint Libraries – Install, description | MS Tech BLOG

    1. Thanks Hans. As Hans points out in this blog post; Microsoft as of yesterday (20/5/13) now released the stand-alone SkyDrive Pro Client. I will post an update to this article now. Much appreciate the tip!

  2. Those standalone exe’s don’t work for a quiet/silent SCCM install. The OST method seems to be the only way to do is right now. Wish MS would fix this.

    1. Hi Dave,

      That’s interesting, I have taken a closer look at the standalone EXE’s and they seem to extract out similar to the Office 2013 media does. At a first guess you might be able to still create a standard MSP package using the OCT following common process that is configured to force the silent install and other customisations for SkyDrive Pro bits only then place this MSP in the ‘Updates’ folder from the extracted standalone EXE and see what happens. I will do some further investigation, test my theory and reply back with a result.

  3. I built msp version using OCT tool, I selected to only install SkyDrive and not to uninstall any Office 2010 products as this is requirement. My problem is that after silent installation, Outlook 2010 crushes on start, it requires Repair. After that, old SharePoint workspace is default sync app again. Another repair on Office 2013 will make sync through SkyDrive but Outlook crashes again. I am after silent OneDrive client installation. What are my options?

  4. Hi Anna, Sorry for the slow response. I understand what your talking about, the challenge with OneDrive / SkyDrive client in Office 2013 is that it actually still ships out from Microsoft as the GROOVE.exe process which happens to be the same process that SharePoint Workspace ran as in Office 2010. This presents the problem in that the new client is supposed to supersede or upgrade SharePoint Workspace so running the two together on the same machine would not be recommended. Is it a requirement that SharePoint Workspace remains in your deployment?

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top
%d bloggers like this: