Integrate Office Update into Build and Capture Task Sequence
The Install Software Updates step works for my Windows 7 Build and Capture task sequence, which also installs Microsoft Office 2010 software; but the installed updates contain only Windows OS updates, not Office updates. I have selected All Software Updates. Can Office Updates be integrated into the Build and Capture task sequence as well? (The Office Updates works for my Deployment task sequence though, which takes time). Thanks and regards.
February 16th, 2012 6:42pm

The best way to install Office 2010 (and 2007) updates is to manually download them, extract the files, and copy the resulting MSPs into the Updates sub-folder of the Office installation directory. All MSPs in this folder are automatically installed as part of the Office installation process.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2012 8:22pm

And Office updates can't be installed unless office is already installed on the PC, so in a Deploy scenario Jason's approach is definitely the way to go! Else you will have to install office prior to ruining the "apply All software updates step". Same goes for build and capture. To patch with office updates, office must be installed.Michael Petersen | My blogs: blog.coretech.dk/author/mip/ and SCUG.dk/ | Twitter: @OSDeploy | Linkedin: Michael Petersen
February 17th, 2012 2:16am

Should I put a 1 in front of the name of my custom setup file from the OCT so it runs that first before the update MSP's?
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2012 3:28pm

To my knowledge, it doesn't really matter as the MSPs don't conflict in any way.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 8th, 2012 3:39pm

Is it true that Office updates won't install during an OSD TS? I have Office installed in a prior step in the same TS and it just ignores the updates step, although will install any Windows updates fine, but ignores updates for any other Microsoft products that were installed in the same task sequence.
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2012 3:42pm

I wouldn't say this is by design, but I do think it does happen for various reasons -- not necessarily all of the time -- but yes, I think it is a "common" issue. What most most do is either what's outlined above or they insert a script into the TS to rescan the system for update compliance and perform an additional Install Updates task (http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/b525aafc-b613-49a2-9015-3ae1c2db2e01/ ).Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 8th, 2012 4:07pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics