• 0

Office Deployment Tools


Question

So, I have been messing  around with Office Deployment Tools to DL Visio 2019 Pro, and Project 2019 STD and having some issues.  Below is an example of what I am using.  I get no errors, but does not seem to download the full package of the programs.  I only see about 230mb of download.

 

<Configuration>
  <Add SourcePath="\\unc\path" OfficeClientEdition="32" Channel="PerpetualVL2019">
      <Product ID="VisioPro2019Volume"  PIDKEY="xxxxx-xxxxx-xxxxx-xxxxx" >
         <Language ID="en-us" />
      </Product>
  </Add>
  <RemoveMSI />
  <Display Level="None" AcceptEULA="TRUE" />  
</Configuration>

 

I am using the following commands to download/install

 

setup  /download example.xml

setup /configure example.xml

 

Not sure what I am doing wrong.  First time using the ODTs. 

Edited by Brandon H
fixed code being in bright yellow
Link to comment
Share on other sites

7 answers to this question

Recommended Posts

  • 0
20 hours ago, sc302 said:

this will create an xml for you

https://config.office.com/deploymentsettings

 

then it is

\\server\share\O365\setup.exe /download \\server\share\O365\whatever.xml

Still not working.  Data downloads the same amount and now nothing happens when I try to install.  Only thing I can think of is that I have the wrong licensing type.  Which the VLSC site shows MAK for the key and unless I am missing something, the channel is perpetual.  Just give me an ISO already....

 

Anyway, here is the new script from the site....

 

<Configuration ID="0beae8b1-1741-4b53-981d-e184d096896a">
  <Add OfficeClientEdition="32" Channel="PerpetualVL2019" SourcePath="\\unc\path" AllowCdnFallback="TRUE" ForceUpgrade="FALSE">
    <Product ID="VisioPro2019Volume" PIDKEY="xxxxx-xxxxx-xxxxx-xxxxx">
      <Language ID="en-us" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="OneDrive" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="PinIconsToTaskbar" Value="FALSE" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="TRUE" />
  <Updates Enabled="TRUE" />
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

 

Don't have much more time to work on it today, but any other suggestions would be appreciated.

 

Thanks

Link to comment
Share on other sites

  • 0

the below works for me in a pdq install package for o365, utilizing an xml generated from that site.

 

"\\server\share\setup.exe" /configure "\\server\share\whatever.xml" 

Link to comment
Share on other sites

  • 0
3 minutes ago, sc302 said:

the below works for me in a pdq install package for o365, utilizing an xml generated from that site.

 

"\\server\share\setup.exe" /configure "\\server\share\whatever.xml" 

I will try another PC tomorrow.  Maybe it is just my test system.

Link to comment
Share on other sites

  • 0

Also, use Notepad++ or another editor if you edit the XML.  I have heard of problems using Notepad or Wordpad.

 

This is OUR XML, but I download and install from THEIR CDN.  I don't download local copy, but we have bandwidth to spare.  We use KMS server to activate. 

 

c:\Installers\Office 2019\setup.exe /configure configuration.xml

 

<Configuration>

<Add OfficeClientEdition="64" Channel="PerpetualVL2019"> 
    <Product ID="ProPlus2019Volume">
      <Language ID="en-us"/>
    </Product>
    <Product ID="ProjectPro2019Volume">
      <Language ID="en-us"/>
    </Product>
    <Product ID="VisioPro2019Volume">
      <Language ID="en-us"/>
    </Product>
  </Add>

  <RemoveMSI All="True" />
  <Display Level="None" AcceptEULA="TRUE" />
  <Updates Enabled="TRUE" Channel="Monthly" />
  <Logging Level="Verbose" Path="%temp%"/>
  <Property Name="AUTOACTIVATE" Value="1" />
    
  <!--  <Updates Enabled="TRUE" Channel="Monthly" /> -->

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

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

</Configuration>


 

Link to comment
Share on other sites

  • 0
19 hours ago, sc302 said:

the below works for me in a pdq install package for o365, utilizing an xml generated from that site.

 

"\\server\share\setup.exe" /configure "\\server\share\whatever.xml" 

Yea, one of my test systems has some issues. I was able to get everything from another test system so all good.

 

Thanks

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.