[ltsb, 1607] Slip steam updates in to image being deployed by MDT / WDS

[kennysarmy]

yeah i forgot to mention you need to extract the cab (this works for 2010 and 2013 so assume 2016 is the same as the /admin option still functions and generates an MSP for controlling the installer)

 

Thanks.

 

I've used an offline WSUS to download all the Office 2016 updates, if I extract all the MSP files from the CABS I end up with many MSP's of the same name, eg access-x-none.msp so they can't all co-exist in the same updates folder, do I have to work out which one is the most recent?

[SHimmer45]

i just took the most recent if there are name conflicts

[kennysarmy]

i just took the most recent if there are name conflicts

 

Sorted!

 

Our image now deploys with zero Microsoft Windows 10 and Office 2016 updates.

 

Thanks.

[NotBatman]

Do you mean adding the updates here?

 

[ATTACH=CONFIG]49466[/ATTACH]

 

I've not tried this method before....

Sorry, I'm terrible at remebering to reply to things, even with push notiifcations. Yes, that's the section on MDT. I see you've got it sorted now already, but this might be another way of doing things. You can just expand that section, find the OS version you want to apply it to, right click, import package, choose the cab file you've downloaded from Microsoft and it'll extract it out and do what it needs to do with it automatically. Basically it'll pull out the MSP and folder it up on the Deployment Share folder.

[ADMaster]

There are scripts out there to collect the msp files from a patched system.

This is the first result on Google

https://github.com/OSDeploy/Microsoft-Office-Updates

 

I use a script like this, but don't recall what site I pulled it from.

It says office 2013, but works for 2016 too.