/build/static/layout/Breadcrumb_cap_w.png

Installing Microsoft Office2019, Project 2019 or Visio 2019 via SDA or SMA

I used this as a guide to download and setup the install https://docs.microsoft.com/en-us/deployoffice/office2019/deploy

you can also find and use the OCT (Office Configuration Tool) from this page.


I will use c:\temp for my install setup, this is your choice.


Create your configuration.xml file for the Office product you want to install. 


Download the office setup.exe from your your MSVLSC or other sources.


Run the setup to download the files to package.

setup.exe /download configuration.xml

this will create a subdirectory "office" under c:\temp


modify the configuration.xml and remove the sourcepath from it

<Configuration ID="9c80d31f-60fd-4a03-9bae-8c9c33ea3339">
<Info Description="admin kms install" />
<Add OfficeClientEdition="64" Channel="PerpetualVL2019" SourcePath="c:\temp" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<Product ID="ProPlus2019Volume">
<Language ID="en-us" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneDrive" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="TRUE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="TRUE" />
<RemoveMSI All="TRUE" />
<AppSettings>
<Setup Name="Company" Value="your company" />
</AppSettings>
</Configuration>
<Configuration ID="9c80d31f-60fd-4a03-9bae-8c9c33ea3339">
<Info Description="admin kms install" />
<Add OfficeClientEdition="64" Channel="PerpetualVL2019" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<Product ID="ProPlus2019Volume">
<Language ID="en-us" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneDrive" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="TRUE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="TRUE" />
<RemoveMSI All="TRUE" />
<AppSettings>
<Setup Name="Company" Value="your company" />
</AppSettings>
</Configuration>

save the file and zip the setup, config file and all sub-directories to a zip file.

Upload the zip to the client drop on either the SDA or SMA

for the SDA create a post task and attach the file


For the SMA attach the file to the software inventory.

On the Full Command Line: you MUST use cmd /c to get it to work correctly

cmd /c setup /configure configuration.xml

Note: the SMA will delete the file from the client drop automatically after upload, You must manually delete it from the SDA client drop.


Project config.xml

<Configuration ID="7f3e0f21-1275-4656-a70a-612bea2a8073">
<Add OfficeClientEdition="64" Channel="PerpetualVL2019" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<Product ID="ProjectPro2019Volume" 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="TRUE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="TRUE" />
<AppSettings>
<Setup Name="Company" Value="your company" />
</AppSettings>
<Display Level="None" AcceptEULA="TRUE" />
<Logging Level="Off" />
</Configuration>

Visio config.xml

<Configuration ID="ce80945a-fbf3-45ca-a71c-a6d08a6bf849">
<Add OfficeClientEdition="64" Channel="PerpetualVL2019" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<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="TRUE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="TRUE" />
<RemoveMSI>
<IgnoreProduct ID="InfoPath" />
<IgnoreProduct ID="InfoPathR" />
<IgnoreProduct ID="PrjPro" />
<IgnoreProduct ID="PrjStd" />
<IgnoreProduct ID="SPD" />
</RemoveMSI>
<AppSettings>
<Setup Name="Company" Value="your company" />
</AppSettings>
<Display Level="None" AcceptEULA="TRUE" />
<Logging Level="Off" />
</Configuration>





Comments

  • Nice article, many thanks for this!
    Just want to leave the link for the office configuration here: https://config.office.com/ - Timokirch 2 years ago
  • Hi, I'm looking for procedures on how to "Upload the zip to the client drop on either the SDA", is this K2000 Media Manager? what is the right way to upload it since this file is too big to be uploaded at the web console. - kore_gio 2 years ago
  • Start - Run - Enter \\ikbox\clientdrop or \\ikbox.domain.xxx\clientdrop and put in name "administrator" and password you set. - SMal.tmcc 2 years ago
    • got it, thank a lot - kore_gio 2 years ago
  • After putting Office 2019 on kace I still get task failed. Looks like the cmd /c setup /configure config.xml is not executing where the setup is. I was wondering how to hard code the path with the task id in that same task so the setup executes from there. Maybe I should ask this on a new topic. Thanks - kore_gio 2 years ago
  • Did you remove the "source path" from the xml prior to zipping the install? if that exists it will always fail. You can verify that by looking on a machine that you pushed the MI to. check C:\ProgramData\Quest\KACE\downloads\xxx\config.xml to see if that is still in there.

    You can bypass quest to test your packaged install from there by opening a admin cmd window and navigate to that dir and run the setup command manually there.

    Note: you get XXX by bring up the MI list page and point your mouse at that MI and look at the bottom of page.

    Note: if you are installing 64bit Of19 to a machine that has prior 32 bit office products it will fail .

    We have used that MI about 50 times now to upgrade we had to run the uninstall for 2016 first on most of them.
    setup.exe /uninstall ProPlus /config config.xml - SMal.tmcc 2 years ago
  • Great write up!

    I did the command cmd /c setup /configure configuration.xml

    Shows the command prompt window and closes after install is completed. Is there a way to hide it? I know you can minimize with a start /min best I remember... Just don't want an end user closing the command prompt window resulting in a failed install. - akilpatrick 1 year ago
    • you would need to use a vb script to hide batch

      https://stackoverflow.com/questions/411247/running-a-cmd-or-bat-in-silent-mode

      or use AutoIT to complie this command into an exe.

      RunWait(@ComSpec & " /c " & "setup.exe /configure configuration.xml","",@SW_MINIMIZE) - SMal.tmcc 1 year ago
  • Gotcha... thank you.

    I added the start /min to it just to see what it would do...

    Here is the command I used:
    cmd /c start /min setup /configure configuration.xml

    This only showed the office icon minimized in the taskbar upon install. This will be fine. Better than a black command prompt window that someone may close.

    Office 2019 is totally different to install than previous versions with an MSI. - akilpatrick 1 year ago
    • Yup and it s the last version that will not be web based. if you want to pin the office apps to startmenu use powershell.

      (New-Object -ComObject shell.application).Namespace('C:\Program Files (x86)\Microsoft Office\Office16\').parsename('excel.exe').invokeverb('pintostartscreen')

      (New-Object -ComObject shell.application).Namespace('C:\Program Files (x86)\Microsoft Office\Office16\').parsename('powerpnt.exe').invokeverb('pintostartscreen')

      (New-Object -ComObject shell.application).Namespace('C:\Program Files (x86)\Microsoft Office\Office16\').parsename('winword.exe').invokeverb('pintostartscreen') - SMal.tmcc 1 year ago
  • I was curious if anyone has gotten the install to work using the SDA Postinstall Task? We have tried, but it will not install, just pauses for about 30 seconds, then moves on with a green check mark. I have tested the installation and XML from command line and it works there. Any suggestions? - dadyjj73 1 year ago
  • That is typical if it does not find the config file. You need the full path. Being in the directory does not seem to make a difference.
    Here is my batch script (note the path for the config call)

    cd\temp\kms

    setup.exe /configure c:\temp\kms\configuration.xml

    c:\windows\w2d\ksleep 10

    exit /b 0 - SMal.tmcc 1 year ago
  • I'm trying to get this method to work with the Retail version of Project Professional 2019(Visio as well). Has anyone had luck using a config file with the retail versions? - bayon 1 year ago
  • Great info everyone, thank you! I am packaging Office 2019 (w/ a VLA license) which is downloaded. As it relates to XML, am I correct in that that path location (e.g. SourcePath="C:\OfficeSetup") needs to be removed and copy the XML file to the root of the install prior to creating the ZIP file and SDA install. I am a bit unclear because I am seeing some different suggestions one being setting the source to %cd%\msoffice.
    Thank you! - JGM 1 year ago
  • I seem to have it working ok however the Office installer get's stuck at a splash screen that seems to hold up any additional tasks completing. Any suggestions on how to work around that? - g1knj99 8 months ago
This post is locked
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ