Rationale for pre-blacklisting of Office Services Packs?

[edanto]

I'm just starting to learn WSUS Offline - thank you to the team that keep it maintained!

I note from the FAQ that Office Services Packs are added to the blacklist by default. I wanted to ask what is the reason for that?

Secondly, the FAQ says that the listed Service Packs "will be implicitly installed if required". In my particular case, I see a WSUS Offline blacklist skip for KB2526086 (Office 2007 SP3), but the machine that I was running it on needs that services pack, so I would have expected it to be installed? What's happening here? Why was it not installed, since it was required (and I presume, present).

Finally - it reports 5 updates as 'not found'. What's a common cause of that please, and how best to rectify?

[boco]

The blacklist for these Service Packs applies only to the dynamic determination of updates from the MS catalog file. If you checked the ''Include Service Packs'' box the Service Packs will be downloaded as they are defined statically.

Secondly, the FAQ says that the listed Service Packs "will be implicitly installed if required".

Means that if the SP is on the medium (the box mentioned above was checked at download) and has to be installed the Patch installer will do so automatically.

Finally - it reports 5 updates as 'not found'. What's a common cause of that please, and how best to rectify?

An example would be a Windows XP installation with Office on it. Both are not up-to-date. You have two media - one for XP and one for Office.
If you now use the XP media to update XP, the Office patches will report as ''Not found'' in that run because they are required by the system but aren't on the current media. They will install later in the Office run.

[edanto]

Thanks - it's nearly clear for me.

One final question, you said "you have two media, one for XP, one for Office" I actually haven't used the Office tab before. When I select things on it, is it possible to make a media that includes both Office and Windows, or must they be run separately?

thanks

[boco]

You can have ''All-in-one'' ISOs. If you execute ./cmd/CreateISOImage.cmd manually you will get all possible command-line parameters. The GUI allows creation of per-OS or All-in-one (x86 only) ISOs.