none
Deploying Office 365 (2016) using MDT to a Windows 10 Task Sequence

    Question

  • Having some problems trying to deploy Office 365 ProPlus using MDT (8443) on Server 2016. The batch file and config.xml I have setup work ok if I run them on a computer manually, but when I put it into MDT to run, it errors out during deployment. I'm basically having it run the command below.

    \\server\deploymentshare$\applications\Microsoft Office\setup.exe /configure \\server\deploymentshare$\applications\Microsoft Office\config.xml

    Below is a copy of the config.xml.

    <Configuration>

      <Add OfficeClientEdition="64" Channel="Current">
        <Product ID="O365ProPlusRetail">
          <Language ID="en-us" />
        </Product>
      </Add>

      <Property Name="PinIconsToTaskbar" Value="FALSE" /> 
      
      <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
     
      <Updates Enabled="TRUE" Channel="Current" /> 

      <Display Level="None" AcceptEULA="TRUE" />

      <Property Name="AUTOACTIVATE" Value="1" />

    </Configuration>
    Monday, May 22, 2017 4:30 PM

Answers

  • My xml looks like this:

    <Configuration>
    <Add SourcePath="" OfficeClientEdition="32">
        <Product ID="O365ProPlusRetail">
          <Language ID="sv-se" />
        </Product>
      </Add>
     
    <Updates Enabled="TRUE" Channel="Current" />
     
    <Display Level="NONE" AcceptEULA="FALSE" />
     
    <Logging Level="Standard" Path="%temp%" />
     
    <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
    <Property Name="AUTOACTIVATE" Value="0" />
    </Configuration>

    And I run it from a .bat file with this in it:

    @echo off
    pushd %~dp0
    echo Installing Microsoft Office 365
    setup.exe /configure install.xml

    I then add it as a application in MDT workbench with the commandline being cmd.exe /c install.bat


    • Edited by Balterz Tuesday, May 23, 2017 12:07 PM
    • Marked as answer by Jay9x Tuesday, May 23, 2017 6:26 PM
    Tuesday, May 23, 2017 11:57 AM

All replies

  • My xml looks like this:

    <Configuration>
    <Add SourcePath="" OfficeClientEdition="32">
        <Product ID="O365ProPlusRetail">
          <Language ID="sv-se" />
        </Product>
      </Add>
     
    <Updates Enabled="TRUE" Channel="Current" />
     
    <Display Level="NONE" AcceptEULA="FALSE" />
     
    <Logging Level="Standard" Path="%temp%" />
     
    <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
    <Property Name="AUTOACTIVATE" Value="0" />
    </Configuration>

    And I run it from a .bat file with this in it:

    @echo off
    pushd %~dp0
    echo Installing Microsoft Office 365
    setup.exe /configure install.xml

    I then add it as a application in MDT workbench with the commandline being cmd.exe /c install.bat


    • Edited by Balterz Tuesday, May 23, 2017 12:07 PM
    • Marked as answer by Jay9x Tuesday, May 23, 2017 6:26 PM
    Tuesday, May 23, 2017 11:57 AM
  • If you install O365 with admin account AcceptEula=TRUE will have no impact. Default is FALSE.

    And because Office 365 Pro Plus is set to activate automatically you should set it to default 0.

    Source: https://support.office.com/en-us/article/Configuration-options-for-the-Office-2016-Deployment-Tool-d3879f0d-766c-469c-9440-0a9a2a905ca8

    Tuesday, May 23, 2017 12:05 PM
  • Thanks Balterz. I didn't know that about the EULA. I did finally get it to deploy by inserting a Run Command into the task sequence instead of Install Application. Thanks for the info on the xml.
    Tuesday, May 23, 2017 6:25 PM
  • Hi Jay9x can you please share the run command you used to make Office365 deploy successfully with in MDT?

    Thank You in advance!

    Thursday, March 1, 2018 9:57 PM
  • nice work. And thanks for sharing. Can you please tell where did you save the Office Deployment Tool and the <g class="gr_ gr_279 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="279" id="279">xml</g> file?

    Thanks in advance

    Thursday, July 12, 2018 2:57 AM