Office updates during build and capture

[apug666]

Hi,

 

Can anyone explain a way to update office during a build and capture task sequence please? I can advertise windows updates to the correct collection and they are found and installed but office updates just don't get applied.

 

I know when using windows update you have to enable updates for other products, is there something else I need to do?

 

Thanks,

 

Al

[RobJanssen86]

Divide the build and capture.

 

So build up an machine with only the build part of the task sequence (disable the rest), scan updates to that machine with the SCCM client, Office updates may be required, install them. If all is one, capture the OS via capture ISO or TS.

[apug666]

I have various advertisements that target different collections of clients, these will install things on to the client that I don't want in the build image. I have tried deploying the patches using the updates folder but that doesn't seem to work if you use an office customisation script. This is far more difficult than it needs to be.

 

There must be a straightforward way to get office updates into a build

[apug666]

Adding the updates to the updates folder doesn't work as the service pack is in there and files get overwritten. When I come to update after the build it shows as still requiring the service pack because it was overwritten by the slipstreamed updates.

 

The only way I can think to get it to work is to download each patch individually and install them as a step in the task sequence.

 

Can anyone help?

[Jaybone]

We dealt with this a while ago, and yeah, it's annoying. I think I actually found the liknk to the solution on these forums, but I can't remember.

 

Anyway, if you grab the script here:

https://msdn.microsoft.com/en-us/library/aa826676%28VS.85%29.aspx?f=255&MSPPError=-2147217396

 

Make a package with it, and run that package in you TS before you run the Install Updates step, you should be all set.

 

 

And in case that link dies:

Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")
ServiceManager.ClientApplicationID = "My App"

'add the Microsoft Update Service, GUID
Set NewUpdateService = ServiceManager.AddService2("7971f918-a847-4430-9279-4a52d1efe18d",7,"")

[apug666]

 

We dealt with this a while ago, and yeah, it's annoying. I think I actually found the liknk to the solution on these forums, but I can't remember.

 

Anyway, if you grab the script here:

https://msdn.microsoft.com/en-us/library/aa826676%28VS.85%29.aspx?f=255&MSPPError=-2147217396

 

Make a package with it, and run that package in you TS before you run the Install Updates step, you should be all set.

 

 

And in case that link dies:

Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")
ServiceManager.ClientApplicationID = "My App"

'add the Microsoft Update Service, GUID
Set NewUpdateService = ServiceManager.AddService2("7971f918-a847-4430-9279-4a52d1efe18d",7,"")

Thanks Jaybone, I've tested this in my task sequence and I can finally patch office in my build and capture!

 

It shouldn't be this difficult, spent ages looking at it!

 

cheers,

 

Al

[Jaybone]

It shouldn't be this difficult, spent ages looking at it!

 

LOL, yeah. In the GUI, it's a simple checkbox - "give me updates for other MS products when I update Windows."

Getting to it from the backend requiring some arcane vbs involving a UUID and the number seven is kind of ridiculous.