[ms office - 2019] Installing 2019 with custom options

[Warwick_Tech]

So another brainwave from MS, you can't create .msp files for Office 2019 - Instead you have to create (you guessed it) and XML file (starting to notice a pattern here)

 

I've gone through the generator https://config.office.com/deploymentsettings

 

And used the switch> Setup.exe /configuration "location of xml file"

 

but it only works when these are copied (and launched) locally, not on a network share, and certainly not automatically via task sequence in MDT -

 

Scratching my head on this one; generic error below

 

Edited December 11, 2019 by Warwick_Tech

[Warwick_Tech]

XML file below (Edited for security)

 

 

So I think ProPlus2019Volume is actually just Office 2019 pro plus PC install, and the switches for licencing are:

"SharedComputerLicensing" Value="0"

"DeviceBasedLicensing" Value="1"

 

Device based licencing is MAK\PID key (?) and one of these options is W10 education only - But I can't remember which one!

[ITGuyNW]

Yeah if we want to run a "remote" install with Office 2019, I do it through PDQ which copies the files first to the local machine then runs installation.

 

I just find it easier to go the CDN route.

[Warwick_Tech]

Yeah if we want to run a "remote" install with Office 2019, I do it through PDQ which copies the files first to the local machine then runs installation.

 

I just find it easier to go the CDN route.

 

Isn't the MSK/PID key saved in plain text so a user could in theory find it?

 

This whole deployment seems like an afterthought

[ITGuyNW]

Isn't the MSK/PID key saved in plain text so a user could in theory find it?

 

This whole deployment seems like an afterthought

 

Where would they find it if they have no access to C:\ ?

[Warwick_Tech]

Where would they find it if they have no access to C:\ ?

 

True, I just don't like plain text keys.

 

Speaking of this issue, I believe I've got it resolved;

 

https://www.thelazyadministrator.com/2018/03/20/remotely-install-office-proplus-update-office-configuration-on-client-computers-with-powershell/

 

There's a powershell command you can alter to go to the remote folder:

 

set-location "C:\Transfer"; .\setup.exe /configure configuration.xml

 

He's also got some funky other scripts, but the other key was apparantly

 

When I ran this remotely it seemed that client computers did not properly update unless FORCEAPPSHUTDOWN was set to TRUE.

 

So alter and add this PS line to your MDT and away we go