Office 2019 Deployment via MDT

[mattpant]

Morning All,

 

I'm trying to create a new windows deployment Task in MDT which includes the install of Office 2019, however it's failing to install, when it get to that part of the deployment, the setup application opens, but then a message appears saying "Couldn't install, We're sorry, we had a problem installing your Office program(s). Is your internet connection working? Do you have enough free space on your main drive?

 

I've downloaded the Office deployment tool and configured the XML file to include the settings / apps etc that I require. I've also used the command to download the install files locally to disk rather than pull the updates from the Office CDN and copy this directory to the Applications Folder on the MDT server.

 

I've amended the source in the XML file to point to the Office Folder within the applications folder on the MDT server - SourcePath="\\MDTSERVERNAME\deploymentshare$\Applications\Microsoft Office 2019"

 

I have this command to launch the setup for the application from within Deployment Workbench:-

 

Quiet Install Command - setup.exe /configure Office2019.xml

Working Directory - .\Applications\Microsoft Office 2019

 

I've read in some articles that if the install/source files are within the same folder, you don't need the source path specified in the XML file, but I've tried removing the line and still get the same error. - I've read a few other guides but nothing really mentions about the source path - it just seems to work!

 

Anyone able to point me in the right direction please?

 

I wish to use the files downloaded locally rather than pull from the internet so it doesn't hog up bandwidth when doing a large scale deployment.

 

Thanks

 

Matt

[mattpant]

I've done a bit more tweaking with the XML file and set the source to "Z:\Applications\Microsoft Office 2019" (The Z drive shows in this PC - and I can access the applications\microsoft office 2019 folder

 

But now I get - "We found a problem - We're sorry, we can't continue because we weren't able to download a required file. Please make sure you're connected to the internet or connect to a different network, then try again"

[ITGuyNW]

I initially wanted to use the local option but I never got it to work either! I even tried copying the files locally instead of a share and it never worked. I ended up having to use CDN which worked first time for me.

[RLR]

Can you post your xml file?

 

It should look something like this

[list]
[*][color=#000000][/color]
[*][color=#000000]  [*][color=#000000]       Channel="PerpetualVL2019" >[/color]
[*][color=#000000]    [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]    [/color]
[*][color=#000000]  [/color]
[*][color=#000000]     [/color]
[*][color=#000000]   [/color]
[*][color=#000000][/color]
[/list]

This will download Office from the net and not use a local version you may have downloaded.

Edited December 3, 2021 by RLR

[mattpant]

Can you post your xml file?

 

It should look something like this

[list]
[*][color=#000000][/color]
[*][color=#000000]  [*][color=#000000]       Channel="PerpetualVL2019" >[/color]
[*][color=#000000]    [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]      [/color]
[*][color=#000000]    [/color]
[*][color=#000000]  [/color]
[*][color=#000000]     [/color]
[*][color=#000000]   [/color]
[*][color=#000000][/color]
[/list]

This will download Office from the net and not use a local version you may have downloaded.

 

Hi,

 

This is the XML file I have created at - https://config.office.com/deploymentsettings PIDKEY has been blanked in the example below, but is correct in my actual XML file.

 

 

I've also tried with the Source Code reading as -

SourcePath="\\SERVERNAME\deploymentshare$\Applications\Office2019x64"

and with the line removed completely but still no luck!

 

Thanks

 

Matt

[jonnykewell1]

I've been having the same issue recently when setting this up at one of our new sites. I ended up using an older setup.exe from another one of our sites using 2019. Something must have changed in the latest release / download and just constantly says it couldn't download a file. It 100% wasn't firewall or filtering related and I compared XML files with the other site. Edited December 3, 2021 by jonnykewell1

[mattpant]

I've been having the same issue recently when setting this up at one of our new sites. I ended up using an older setup.exe from another one of our sites using 2019. Something must have changed in the latest release / download and just constantly says it couldn't download a file. It 100% wasn't firewall or filtering related and I compared XML files with the other site.

 

I'm just trying again with an old setup.exe file I've found from previous - so fingers crossed!!

 

If not... I don't suppose your able to send me a copy of the setup.exe that is working for you are you?

Edited December 3, 2021 by mattpant

[LeMarchand]

Don't have SCCM, but this seems to work for us:

 

Startup Script:

 

@ echo off

If EXIST "C:\Program Files\Microsoft Office\Office16\" goto :FINISHED

"\\Server\Location\Office2019\setup.exe" /configure "\\Server\Location\Office2019\Configuration.xml"

:FINISHED

exit

 

The location pointed to holds the setup.exe, various xml files (staff machines get more apps than pupil ones), and the Office folder originally created which contains a data folder containing a couple of cab files and another folder with more cabs and a couple of dat files.

 

The xml is:

 

 

Obviously parts of your one will vary. I don't think this only installs from the folder (mainly as my first-time update run never has any Office product updates and sometimes takes a while) - but it does install!

[mattpant]

OK - Just tried a deployment again using an old setup.exe and it failed again with the same message.

 

These are the versions I've tried -

 

setup.exe 16.0.14527.20144 - 7.72MB - this was the latest file that downloaded from the Microsoft website

 

setup.exe 16.0.11617.33601 - 5.04MB - this is an older setup file that I'd previously downloaded and use when I've done a manual install from a different network install folder on existing computers.

[LeMarchand]

If it's any help, ours is 16.0.11306.33602, 4.94 MB. The cab/folder is labelled 16.0.10340.20017.

[FirstClass]

Mine works perfect from MDT.

 

This is my XML File

 

[jonnykewell1]

Sorry missed your reply, if you do want to try the same version as me still, drop me a message and I'll look at sharing it with you.

[mattpant]

Sorry missed your reply, if you do want to try the same version as me still, drop me a message and I'll look at sharing it with you.

 

Thanks - will PM you know!

[mattpant]

Mine works perfect from MDT.

 

This is my XML File

 

 

Does this XML file pull the files in directly from the internet then with this setting "AllowCdnFallback="TRUE" as you have no reference to a local source directory - I'm trying to avoid this to save on bandwidth and have the setup files already downloaded locally to help speed up install.

[mattpant]

The mystery continues!

 

I've noticed that Office 2021 is available for download and I've created the XML config files for that - downloaded the source files locally - added it into MDT and...

 

THIS WORKS!

 

But doing the same thing with 2019 doesn't!

 

Weird!

[D2bromwi]

I have the same issue today with the latest version. It seems Office 2019 doesn't like the en-gb. Swap to en-us and all works.