- this is a video over an hour long, including demonstration of using the deployement tool
1. I opened the ISO from MSDN and extracted that to D:\Archive\Office2016\ which created subdirectories off of that of \Office\data
-- Note that if you don’t have the iso yet, you can can ask setup to download the required files, just skip ahead to step 3 below---
2. rename D:\Archive\Office2016\setup.exe to whatever the heck you like.
3. I downloaded the Office 2016 Deployment Tool (http://www.microsoft.com/en-us/download/details.aspx?id=49117) and
extracted the zip to D:\Archive\Office2016\. This will place setup.exe and configuration.xml into that directory (this is why we renamed setup.exe above). I edited the XML file and put the following in it (deleting everything else that was in it):
NOTE: you can setup the deployment to include multiple languages ie:
<language ID= ‘en-us’ ‘es-es’/>
Using group policy, there are over 2100 settings you can control via the deployment tool
***NOTE that I wasn’t sure about the naming convention for Skype for Business/Lync so I put them both in the config file - I still don’t know which one is needed but the above config successfully did NOT install Skype for Business***
4. If you don’t have the ISO then run the following: D:\Archive\Office2016\setup.exe /download configuration.xml
that will create the sub directories and download the files necessary for your desired configuration
5. Now, whether this is from the ISO or the downloaded files, run: D:\Archive\Office2016\setup.exe /configure configuration.xml
bingo, bango, bongo, you’ve got a customized install.
I tried your method, and when I launched the program from CMD, I immediately got error code 30088-1021 after it got elevated privileges. If instead of using cmd and the deployment toolkit’s setup file, I went into \office directory (one level down
from where I was) and launched the setup64 program and it began installing correctly. I do have Office 2013 installed still.