Custom Support Program metadata kb numbers differs

Question

Hello,
I am using SCCM 2007 R2. We are in the middle of migrating XP to W7 so our company stepped into the Customer Support Program to receive XP updates.From the MS connect site I can download cab files and the executables. I downloaded the wsusimporttool.exe
and using this command I succesfully injected updates in WSUS. SCCM sync is then succesfull but there it goes wrong. The KB exe's I downloaded are mostly different then the Customer Support patches I see in SCCM.
For example: the month May the title of the kb article to download is kb2962482. The executables I downloaded from there are named kb2953522. In SCCM I see only kb2926765 tagged as Custom Support update. Results of the import using wsusimporttool.exe are
no failing to import but I do see a number of updates with missing files. The kb article updates mentioned there are not available in the Custom Support connect site. It drives me crazy. What am I doing wrong?
The search folder criteria in SCCM I use is Program: Windows XP SP3 Custom Support OR Windows XP SP3 Important Update - Custom Support AND Expired: NO AND Superseeded: NO.
Thanks in advance

Answer 1

Who can help me sorting out where it goes wrong?
I'm confused. You have access to these out-of-support Windows XP patches, which tells me you have a Premier Support contract with Microsoft. Why not just open a ticket?
Per the instructions, are the files actually IN the payload directory (e:\WSUS Extended Support\Payload).
Does the payload directory and do those files have the correct ACLs?)
ie7-windowsxp-kb2953522-x86-custom-nld.exe with file digest 197821D533AA3F006F41A53665D6ABAC7D49C627
ie7-windowsxp-kb2953522-x86-custom-enu.exe with file digest 30C1D8A71B424842E3E022AC033B7E46B11CD11B
windowsxp-kb2926765-x86-custom-enu.exe with file digest 8FD292E3EA4DDB1CC644813203FFD1F5DCA00F23
windowsxp-kb2926765-x86-custom-nld.exe with file digest D91F6179B8F0E6A54FA0F445F0A097EB3EBF88C1
    --------------------Summary-------------------
        Attempted to import:              4 updates
        Failed to import:                     0 updates
        Updates with missing files:               4
     --------------------Summary-------------------
It looks to me like this is the core issue, becuase the fundamental issue here is that the import cannot find those files, and thus the import failed.
Which also begs another question: Are you still running *IE7* on these Windows XP systems???
Step 3 is not necessary for me to do (SCCM 2007)
I'm not sure where Chad got this idea, and anytime I've added a new product category to a SUP in a CM2007 system, I've always had to go back to the SUP Component Properties and enable it for sync. There's no harm in doing so, so I would suggest ignoring
the advice in Chad's article and do it anyway.
Step 4 the wsyncmgr.log looks normal too.
It would. Your failure is with the import to the SUP, not the SCCM sync FROM the SUP.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.