Import Update (Service Packs) using catalog does not show up in WSUS console

Answered Import Update (Service Packs) using catalog does not show up in WSUS console

  • 14 aprilie 2012 17:59
     
     
     

    I have installed WSUS 3.0Sp2 on windows server 2008 R2. Did all the settings according to documentation and is working fine with respect to synchronization and deploying on client workstation. The only problem until I face is that it failing to download service packs(windows 7 sp1 /office 2007 sp3 etc tried until now) and its here that I decided go by the Import Update function using Microsoft update catalog. It smoothly displayed the service pack imported directly to wsus successfully but when I try to locate it in wsus administration console I don't see it anywhere which baffles me to no limit. Where did it go if it really imported(wsus content folder!!!!) as I dont see it normally.

    I am badly struck with this and would highly appreciate if any one comes up with some useful ideas to make it working for me..Deployment of service packs is a must for us....

Toate mesajele

  • 15 aprilie 2012 01:56
     
     

    Hi,

    confirm you have selected/enabled the relevant Languages/Products/Classifications:
    http://technet.microsoft.com/en-us/library/dd939924(v=ws.10).aspx


    Don

  • 15 aprilie 2012 06:48
     
     

    Thanks for your reply Don. Yes, I have already selected the relevant product and classifications. Language chosen is English only as I just need that only. Any other helpful ideas please...

  • 15 aprilie 2012 07:35
     
     

    Btw, where did the service pack go which I imported using Update catalog?? Any idea how to trace it to deploy to clients???

    I am still in a spin with that regard.

  • 15 aprilie 2012 09:47
     
     

    a few thoughts:

    check C:\Program Files\Update Services\LogFiles on the WSUS server

    Event Log (Application) on the WSUS server (look for WSUS events)
    Event Log (System) on the WSUS server (look for general events which impact WSUS like connectivity, timeouts, diskspace)

    check WSUS console - Download status / queue ??

    check on the WSUS server: bitsadmin /list /allusers /verbose

    consider wsusutil (may reveal ill health, or throw errors, indicating a reset needed etc)

    review for inspiration:
    http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/c00a5700-eb40-47a4-99d5-423b0513eb06

    http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/3ad50f93-35a1-489f-b95a-c2e8c4886429

    http://social.technet.microsoft.com/wiki/contents/articles/wsus-troubleshooting-survival-guide.aspx


    Don


  • 15 aprilie 2012 09:48
     
     

    Btw, where did the service pack go which I imported using Update catalog?? Any idea how to trace it to deploy to clients???

    logfiles/events should reveal what did (or didn't) happen during the import attempt.

    Don

  • 15 aprilie 2012 17:18
     
     

    wsus eventviewer log shows the following error

    "Content file download failed. The server does not support the necessary http protocol. BITS requires that server supports the protocol range header"

    This must be the real cause of download failure of service packs. However, can we fix it coz we are not using any proxy server for downloads. I am still unsure of what happened to Imported service pack which still doesnot show anywhere to be deployed although it showed successfully imported from update catalog of microsoft.

  • 15 aprilie 2012 17:46
     
     

    Also, one more question..Can we import separately downloaded *.exe file into wsus using import update or not..if yes, please guide how to....

  • 15 aprilie 2012 19:45
    Moderator
     
     Răspuns

    "Content file download failed. The server does not support the necessary http protocol. BITS requires that server supports the protocol range header"

    Which is also why the original attempt failed as well. Importing updates gets you nothing different than synchronizing; ergo, if the update is synchronized, and you can approve it, there is no value in using "Import Updates".

    In the instant case, the download of the installation file is failing because you have a network device in the pathway between the WSUS server and the Internet that is not fully compliant with the HTTP v1.1 protocol specification (now 12 years old) regarding the use of Range Protocol Headers. The 'fix' is to properly configure, or update the firmware, or replace if too old, the device so that it is HTTP v1.1 compliant.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

  • 15 aprilie 2012 19:46
    Moderator
     
     

    Can we import separately downloaded *.exe file into wsus using import update

    No. The binaries must be downloaded from Microsoft by the WSUS server.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

  • 16 aprilie 2012 06:35
     
     Răspuns

    Thanks for your reply lawrence. I was under a notion that import update function will import entire software package rather than mere synchronization. This is why I was wondering how come it shows imported successfully so quickly even a service pack of size 600-700MB. Neways, regarding HTTP1.1 specification, we use cyberoam UTM as Gateway Firewall and until its firmware is upgraded to support http1.1 , I found the following link to solve my Problem of downloading service packs using wsus..

    http://support.microsoft.com/kb/922330

    Apparently, I am able to download service packs now after following the instructions in it.