SCCM Office 2019 Deployment

[T_Lister]

So I've used the SCCM Office Download tools, and I've downloaded the Office deployment tools for Office 2019. If I run the usual command line on a computer setup /configure config.xml, it installs no problem. Deploy it via Application or Task Sequence, automatic or manual install, all I get is:

 

"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 etc etc..."

 

Am I missing something obvious? I've done exactly the same with Office 2021 LTSC and that works perfectly, so the problem is clearly 2019 related. And 2019 is what we want for now.

[CHiLL]

My deployment lives in the Apps folder on the SCCM server. Within the Office 2019 folder lives my config.xml and setup.exe. There is also a sub folder called "office", which is where it downloaded the install files to. Here's a slightly modified version of my config.xml:

 

My app deployment has the content location defined as the folder that has setup.exe and config.xml and the install is defined as:

setup.exe /configure config.xml

I hope that helps.

[T_Lister]

 

 

setup.exe /configure configuration.xml

 

 

This is what I already have in. Looks the same to me other than my Shared ComputerLicensing value? As mentioned, the setup for 2021 is identical to this, which is what is baffling me. And as I can do a manual deployment via cmd, it must be something in SCCM?

[Steve21]

 

This is what I already have in. Looks the same to me other than my Shared ComputerLicensing value? As mentioned, the setup for 2021 is identical to this, which is what is baffling me. And as I can do a manual deployment via cmd, it must be something in SCCM?

 

Few things that would be worth checking

 

How old is your version of ODT (setup.exe) as often the old versions stop working with the download stage, and it needs updating before it'll run (https://www.microsoft.com/en-us/download/confirmation.aspx?id=49117) - If you're using an old one, just extract that download and replace setup.exe (then redistribute to DP)

 

By default setup.exe will look into it's own folder for the install files, and not go to the internet (So you shouldn't get that error normally). Did you run the /download stage with setup.exe before deploying to SCCM? (If you did it after remember to redistribute package to update DP). It'll then download the base source files to the Office/data folder within your setup.exe location and it uses those for the base install

 

But it could always be something as stupid as your system account doesn't have proxy access etc if you aren't using transparent, as it'd run as the service rather than a user (when running it manually). If you manually download the source files, and then edit your XML to use SourcePath with a UNC path, does that work? (Just as a test to see whether it's the actual application/XML config it's not liking via SCCM, or whether it's something like internet access as that'd exclude any internet queries

 

Steve

[T_Lister]

I've tried it with old tools, new tools and the SCCM auto package builder. /Download, no problem. Go to the machine, cmd UNC setup.exe /configure and it works. It is solely SCCM that it won't work with. Rather frustrating. By the end of the day yesterday I was starting to look at whether it is something to do with the firewall as we do use a proxy. But if it works as a CMD deployment, why would the firewall block an SCCM deployment?

[CHiLL]

But if it works as a CMD deployment, why would the firewall block an SCCM deployment?

The main reason I can think if is that when installing via CMD, it's running in the context of the logged on user and authenticates to the web as that user. However SCCM uses the SYSTEM account to install, which cannot authenticate to the web like a user can.

 

I think when I configured my Office 2019 setup, I used SCCM's built-in option to create the package: Software Library > Office 365 Client Management > Office 365 Installer. I followed the wizard and created the settings via the "Go to the Office Customization Tool". Once the app was created, I made some basic modifications, like rename, icon, move the app to a subfolder in Application Management, installation timeouts, etc. Then I deployed it.

[Koldov]

Just out of interest, could you try this in your XML...?

 

''

 

http://www.edugeek.net/forums/office-software/227339-deploying-office-2019-a-2.html#post1949731

[2097]

So I've used the SCCM Office Download tools, and I've downloaded the Office deployment tools for Office 2019. If I run the usual command line on a computer setup /configure config.xml, it installs no problem. Deploy it via Application or Task Sequence, automatic or manual install, all I get is:

 

"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 etc etc..."

 

Am I missing something obvious? I've done exactly the same with Office 2021 LTSC and that works perfectly, so the problem is clearly 2019 related. And 2019 is what we want for now.

 

We have a batch that does the install via SCCM ( As a package though )

 

setup.exe /configure Remove.xml
setup.exe /configure Config2.xml
RD /S /Q "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office Tools"
exit /B %EXIT_CODE%

 

Our Config is the following

 

Also just to verify you have down this first

 

setup /download configuration.xml

 

That create the office folder required to install

 

Then to install it is

 

setup /config configuration.xml

Edited May 12, 2022 by 2097

[T_Lister]

Very much the same. Changing the Language ID hasn't really done anything either. We're thinking now we'll look at jumping to 2021 over the summer instead.

[2097]

Very much the same. Changing the Language ID hasn't really done anything either. We're thinking now we'll look at jumping to 2021 over the summer instead.

 

I have just built my 2021 package Same as my post above.

 

Not much of an improvment... But worth it if you are paying for MS agreement.

[IAMCloud_Curt]

I've just had the same issue - kept getting Can not download the required file on the installer.

 

I changed language from en-gb to en-us in my config.xml and it's worked a treat.

[T_Lister]

I've just had the same issue - kept getting Can not download the required file on the installer.

 

I changed language from en-gb to en-us in my config.xml and it's worked a treat.

 

 

I'm sure I'd tried that. Sorted my 2021 KMS out and we're just going to jump to that. Makes sense in a way as it looks the same as Office 365 that you would typically have at home.

[aac]

I had this issue with Office 2019/21 using ODT. Just could not get it to deploy with SCCM no matter what options I selected in the ODT. In the end I build the package using the Office 365 client installer option in the Office 365 Client Management section of SCCM (Current Branch) it creates the package and distributes it for you. Deployed fine...