This was something of a puzzle for a few earlier today.
For a client, we needed to manually add an update to WSUS, to sync with SCCM for deployment. As one would expect, I launched Update Services, then right-clicked my server to launch the import update UI.
However, upon launching the Update Catalog, no checkbox is available to ‘Import directly into Windows Server Update Services’. Instead, the only option is to download the update content to a local directory, which is much less useful.
You may experience the following when trying to add a few of this month’s updates to your deployments.
The symptom is that all of your other updates will download without a problem, only a few will have this warning. Furthermore, these updates with issues do not show any special error messages when viewed in the patchdownloader.log.
The reason for this is that if you deploy your updates in English only, you will find that there are no content files available in English. You can verify the available languages by clicking the updates themselves in the updates list.
‘Applicable Languages : Arabic’ DOH!
This means that the update source is not available in the language you specified while Deploying Updates (perhaps in your templates?).
But how to we deal with this?
Well, if the update refers to a specific foreign language IME (like the one for Chinese character input below) and your organization doesn’t deploy in Chinese, then you can safely ignore it. For the other updates, it is more a case of knowing your organization. If you might deploy, or don’t know if you are deploying in the Middle East, you may be safer just downloading and deploying the content.
If anyone is curious, these were the problem updates for this month, and the associated language:
Update for Microsoft Office 2010 (KB 2598285)
Update for Microsoft Powerpoint viewer 2010 (KB 2553351)
Security update for Microsoft Office 2010 (KB 2687413)
Kudos to Wayne Hughes and Jeff Renfroe for helping me to understand this.