I was struggling with this topic for a while and since there are literally ZERO resources on it on Uncle Google, I thought I will share what I came up with.
What I needed:
- I needed to deploy OneDrive for Business sync app to multiple clients, using automatic approach such as SCCM or group policy, possible as seamless as possible. Users should not have to do anything at all.
- My users are using Office 2010 and there was no way I could have just installed Office 2013 for all of them. I needed to retain Office 2010 but add OneDrive for Business 2013.
What did not work:
- Standalone OneDrive for Business client available for download from Microsoft site is useless, it is not silent install and it would require users to install it themselves
- Creating a custom Office 2013 installation using Office customisation tool that only installs OneDrive was very sketchy. At some point I thought it will work as a silent way. But soon I realised that it was breaking Office 2013 install (e.g. Outlook was not working anymore). Users had to “Repair” Office 2010.
- Using Office Deployment Tool with custom configuration xml file, you need to first download GrooveRetail files then you can run it. Detailed steps below.
Steps to create silent installation package for OneDrive for Business
- Download Office Deployment Tool http://www.microsoft.com/en-us/download/details.aspx?id=36778
- Unpack exe file, you will end up with a folder with some files, most important is setup.exe and configuration.xml file
- Edit configuration file
<Configuration> <Add SourcePath="\\server\share\officedeploy\" OfficeClientEdition="32"> <Product ID="GrooveRetail" > <Language ID="en-us" /> </Product> </Add> </Configuration>
- Product ID should be GrooveRetail – that is OneDrive for Business (previously SkyDrive for Business, previously SharePoint Workspace 2010, previously Groove 2007…) ClientEdition would be either 32 or 64. If you have Office 2010 32 bit, you need to install OneDrive 32 bit, 64 bit will fail to install.
- Source Path should be a path to your OCT folder, at this stage it does not need to be a network share, it can be just d:\officedeploy\ I will come back to importance of permissions in next steps
- Open command prompt or powershell window as Administrator
- Navigate to the location of your setup.exe file
- Run command: setup.exe /download d:\share\officedeploy\configuration.xml
- Now, Russian roulette starts here, the program will actually not give you any progress or indication anything is happening. Check out sources folder, it should start getting filled with some dlls and other files. Files are being downloaded from the internet. You need to have a Internet connection for this to work. If you are behind a proxy or firewall, e.g. you are in corporate network, something may be blocking this download. You may have to bypass corporate proxy or use Internet connection at home. Expected behaviour will be that the program finishes successfully and you will find at list a gigabyte of files in your office deploy folder. That is a half of success.
- Create a network share for your officedeploy files location.
- Add necessary permissions for network share – it is important to add everyone to be able to Read the folder. Also, “domain computers” account have to be able to access this share (Read and Execute permissions), because installer actually uses computer account to copy files across during installation.
- Run \\server\share\officedeploy\setup.exe /configure \\server\share\officedeploy\configuration.xml on the machine you want to install OneDrive for Business. This will install OneDrive for Business, you will notice some Office popup in a notification area if you are installing when being on the machine
- If something fails, check %temp% for some installation log files
- After that finishes you can check if you have OneDrive for Business in Add/Remove programs. You will notice that there is your old Office 2010 intact and new Office 2013 in Programs. This is normal as OneDrive for Business is part of Office 2013.