Office 2016 Updates Folder

[smarties11]

Hi All,

 

Trying to get my head around how to install a fully updated copy of Office 2016, from scratch? I'm deploying Windows 10 at the moment and want Office 2016 to be fully up to date at first install (via SCCM) rather than having to rely on WSUS/SCCM to update after the first install. I've read the various articles about placing the .msp files in the \updates folder of the installation, however getting these .msp files doesn't appear to be easy.

 

I've found this https://docs.microsoft.com/en-us/officeupdates/msp-files-office-2016, an official list of .msp files that have been updated since Office 2016 was released - however I'm not sure how to read the table? There are three columns with applicable KB links to downloads - Non-security, Security and superseded. The problem is, when you download these files and extract them, the .msp files inside all have the same names!

 

So for example, looking at access-x-none there are three downloads - Non-security (02/01/18), security (10/07/18) and security superseded (non-dated). Assume we can ignore the security superseded, but what about the other two? Does the security release include non-security fixes, and vice versa? Sometimes the security release is newer than the non-security and vice versa.

 

I've read about getting an installation on a dummy machine up to date using Windows update, and then using some vbscript to suck out the .msp files but I can't get windows update to pull in Office updates on Windows 10. If I go in to advanced settings on windows updates and tick the option to download updates for other MS software, that setting just unsets itself when I check for updates! And I can't check for updates from within an Office app as we are running a volume licenced version so there is no option to do so!

 

Any ideas?!

 

Thanks!

[DannyG555]

Hi Smarties,

 

I looked at this exact same issue not so long ago. In the end I found a really good powershell script by Mick Pletcher (see below link) that extracts the updates from the distribution folder where SCCM puts the office 2016 updates, uniquely renames them with the KB number, and then places these in to the "updates" folder of the Office 2016 source folder. All you need to do after running it is update the package from the source files! It is possible to automate all of this too.

 

https://mickitblog.blogspot.com/2016/06/powershell-automatically-populate.html

[smarties11]

Cheers Danny - that looks spot on. I'll check it out!

[markwilfan]

I did this in the summer and it broke my deployment. Made every copy of office reconfigure after being installed cleanly. Worst this was it needed admin rights to finish so I binned the idea of slipstreaming