Custom install gone?

One might naively assume the main "product launch contraint" would be that it works and is complete.

They are what they are.

When you dance with the devil,one should take into account that it is after all,the devil.

All right folks ,here's the lowdown from one of my contacts @M$ (an office MCT).

It appears as if because of product launch constraints,the functionality for a custom install was left out.

My feedback was, it will be forthcoming in one of the updates.  

So M$ is aware of the issue.

So should we expect an option for custom install in the near future, as in maybe a decade?

It's possible we may see it tomorrow as part of the VL release - I've heard conflicting reports so this is little more than a guess.

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.

This is the configuration.xml file I made;;

<Configuration>

<Configuration>

  <Add SourcePath="E:\to keep\bittorrent\en_office_professional_plus_2016_x86_x64_dvd_6962141\office extracted" OfficeClientEdition="64" >

  <Product ID="proplusretail">

  <Language ID="en-us" />

  <ExcludeApp ID="Access" />

  <ExcludeApp ID="onenote" />

  <ExcludeApp ID="Grove" />

  <ExcludeApp ID="Groove" />

  <ExcludeApp ID="Lync" />

  <ExcludeApp ID="skypeforbusiness" />

  </Product>

  </Add>

  <Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

</Configuration>