Workaround for Installing Office Updates During an Image Build

Posted on Updated on

Ran into an interesting situation with an image build.  I created a custom Office 2010 SP1 install using the OCT.  During execution of my image build task sequence, Software Updates was not detecting any of the updates for Office.  Further diagnosis revealed that the OCT-built install did not put its “hooks” into the Windows Update Agent, therefore neither the SUP or Microsoft Updates could detect for Office updates.  (Side note: once the image was sysprepped, captured, and added into a deployment task sequence, the updates were suddenly available and installed.)

While the cause as to why an OCT-built Office 2010 SP1 install prohibits installation of updates has not been found yet, there is a workaround to run a script that forces Microsoft Update (e.g. WUA) to receive updates for “other products”.  By executing the following VBScript after installing Office, SCCM Software Updates will then be able to install the updates during the image build task sequence.  The original code is from a TechNet blog post, I just added some extra logging for troubleshooting.  Also, if your TS advertisement is configured to “run from server”, then the script will cause the TS to fail.  To get past this, simply copy the script locally first then execute it from that location.

Const ForAppending = 8
Set oFSO = CreateObject ("Scripting.FileSystemObject")
Set oLogFile = oFSO.OpenTextFile ("C:\ConfigOfficeUpdates.txt", ForAppending, True)
oLogFile.WriteLine "Starting execution of VBScript to configure Office to use Microsoft Updates"
Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")
ServiceManager.ClientApplicationID = "My App" 

' add the Microsoft Update Service by GUID
Set NewUpdateService = ServiceManager.AddService2("7971f918-a847-4430-9279-4a52d1efe18d",7,"")
oLogFile.WriteLine "Script completed successfully"
wscript.Quit(oLogFile.Close)

Advertisements

3 thoughts on “Workaround for Installing Office Updates During an Image Build

    Tom Aguero said:
    August 27, 2012 at 12:03 pm

    Did you set this as a run command line in the TS or did you create a package for it and use the Install Software TS step?

      N. Moseley responded:
      August 27, 2012 at 1:08 pm

      Generally speaking, I have a single package with any and all scripts that are used for deployment task sequences. I’ll then use a Run Command Line step in the task sequence, selected to use the content from a package.

    Willkommen im Zwielicht said:
    December 16, 2014 at 4:27 pm

    Windowsupdate in Windows 7 aufbohren

    Seit Windows 8 hat Mikroweich ja die Website, mit deren Hilfe man die Windows-Update-Funktion von Windows 7 auf alle installierten Microsoft-Produkte ausweiten konnte, still und leise abgedreht. Bei der Suche nach einer völlig anderen Sache hat das Net

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s