Creating Volume Licensed App-V Office 2016 package using ODT

Although MS have withdrawn the option to create a Volume Licensed version of Office 2016 it is still possible to do by the power of the internet :)

Near the bottom of this article is a post by Robert Gijsen on Monday, April 10, 2017.  I have tested his instructions successfully.
https://social.technet.microsoft.com/Forums/office/en-US/367938d8-9210-4c8f-aa5e-c8de41c0a7ca/odt-2016-invalid-product-proplusvolume-specified?forum=Office2016setupdeploy

Robert has provided the older ODT version for download here:  THANK YOU !
https://1drv.ms/u/s!ApkCUv0wQm8UgwFgwRzJXD4N3H-R

Getting this done was not easy.  I would advise keeping the paths as short and simple as possible. Also I did seem to get success by making sure that HKCU\Software\Microsoft\Office\ClickToRun had been deleted or renamed after a run attempt.

Here is my ODT setup.exe configuration file:

<Configuration>

  <Add OfficeClientEdition="32" Channel="Current">
    <Product ID="ProPlusVolume">
      <Language ID="en-us" />
    </Product>
    <Product ID="VisioProXVolume">
      <Language ID="en-us" />
    </Product>
    <Product ID="ProjectProXVolume">
      <Language ID="en-us" />
    </Product>
  </Add>

  <!-- Updates disabled while an update folder location is decided. -->
  <Updates Enabled="FALSE" Channel="Current" /> -->

  <!-- Install Mode Settings -->
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="%windir%\custom\installlogs" />

  <!-- Packager Mode Settings - Sets the App-V Package GUID -->
  <Property Name="PACKAGEGUID" Value="PutYourGUIDHERE"/>
 
</Configuration>

Run
setup /download <FullPathToXMLConfigFile>

Create the folder where the App-V package will be output to.

Then
setup /packager <FullPathToXMLConfigFile> <App-VPackageOutputFolderPath>

if that fails then you can do the magic command posted here by Trausti Sigurbjörnsson
A failure results in HKCU\Software\Microsoft\Office\ClickToRun\LastScerarioResult = Failure

browse to C:\Users\<user>\Appdata\Local\Temp and Copy "Microsoft Office" folder to "C:\Temp" and then rename it to MSO

After That run following command:
C:\Temp\MSO\root\flattener\flattener.exe /Source:"C:\Temp\MSO" /Dest:"C:\Temp\Office 2016 AppV" /Version:"16.0.8067.2115" /ProductReleaseIDs:"ProPlusVolume,VisioProXVolume,ProjectProXVolume" /Cultures:"en-US,x-none" /Platform:"x86"

For the above command you can determine the version number by checking in the registry for the versions written during the OfficeClickToRun.exe phase.

HKCU\Software\Microsoft\Office\ClickToRun\ProductReleaseIDs\2601BB9E-AEBE-441E-A166-5652BF9B61C3\ProjectProXVolume.16\en-us\Version


Error Code Meanings
error 0-1010 (0)  - check your XML in the XML config file.

The App-V package requires the App-V Client setting EnablePackageScripts = 1.  This is because there are scripts coded into the AppVXManifest.xml file within the .appv package file.  MSI installers are being called to install integration components such as the KMS server licensing items.