Setting up a scripted install of Microsoft Office and we have a Office 365 subscription.  Microsoft does not allow you to use the VLK media and still claim the licensing included with Office 365.  I found that Microsoft Office 365 has a Deployment Kit, but don't rely on their directions to walk you through it easily.  I like quick/easy/works every time so I worked through the process and wanted to let everyone know.  This is quick, easy, and is now working every time for me.

First off, start with the Microsoft Office 365 Deployment Tool.  https://www.microsoft.com/en-us/download/details.aspx?id=49117

The instructions for using it are also on that page, but quite honestly, they are incorrect in some places, and assume some wrong things in their directions.

The instructions I include will have a basic configuration page, I have found the page for the details on what to put in the configuration page is good, but doesn't always show where it goes in the config file, so some trial and error will be required.  https://technet.microsoft.com/en-us/library/jj219426(v=office.15)#BKMK_QuickReference

Save the Deployment Tool in a location and run the .exe file.  After accepting the license you will be prompted for a location to extract the file.  For the purpose of this document I will say c:\O365DeploymentTool.  That will extract 2 files, setup.exe and configuration.xml

From a command prompt, change directory into c:\O365DeploymentTool

Run 'setup.exe /download', this will download the code from the Internet and save it into a sub-folder named Office.

To run with the /configure option that you use to install, we will need to know the exact version that was downloaded.

Once it is complete, go into the c:\O365DeploymentTool\Office\Data.  You will find a v32_<versionnumber>.cab file based on the version that was downloaded.  In this example mine was v32_16.0.7070.2026.cab. 

Microsoft documentation will tell you that the same configuration file will work using the /configure option, and that version number isn't required.  I will tell you from experience that if you do not add version number to your configuration.xml file, it will look for v32_.cab, which does not exist. 

Also, we have several options in the Office 2016 deployment that we do not want to install.  Those options are listed in the .xml reference page listed above, but here is the current list

The following is a list of the supported values for ID:

• Access

• Excel

• Groove

• InfoPath

• Lync

• OneDrive

• OneNote

• Outlook

• PowerPoint

• Project

• Publisher

• SharePointDesigner

• Visio

• Word

The value “Groove” is used to exclude OneDrive for Business.

The value "OneDrive" is used to exclude OneDrive, which is the personal online storage service.

The value "Lync" also applies to Skype for Business. 

Here is my configuration.xml file that I use

After the config file is updated I prepare the PO task by zipping up the contents of c:\O365DeploymentTool (not the O365DeploymentTool folder itself, just the contents)

Upload that into your PO task

The parameter must have the name of the configuration file in quotes or it will not work.

setup.exe /configure "configuration.xml"

Hope this saves everyone a lot of time.  First time posting, ignore any typos or formatting issues.