This Computer has not reported status yet

Discussion in 'Windows Update' started by bzumwalt99, Jun 26, 2008.

  1. bzumwalt99

    DaveMills Guest

    Try resetting the winhttp proxy setting to those of IE using

    cfgproxy -u
     
    DaveMills, Aug 2, 2008
    #21
    1. Advertisements

  2. This only tests connectivity in *your* context. It doesn't test connectivity in
    the *WinHttp* context, which has different proxy settings configured per your
    earlier post.

    Dave's suggestion sounds like your best bet.

    Harry.
     
    Harry Johnston [MVP], Aug 4, 2008
    #22
    1. Advertisements

  3. Hi All,

    NOTE 1
    ~~~~~
    I have had this problem and been at it for nearly three weeks,. MS has found
    that there was a problem with a DDL in WSUS. Go to
    http://support.microsoft.com/kb/954960. There you will find a hotfix that
    replaces dll file
    %ProgramFiles%\Update
    Services\WebServices\ClientWebService\bin\Microsoft.UpdateServices.WebServices.Client.Dll.
    Click the Version tab. The file version is 3.1.6001.66 is the new version.

    NOTE 2
    ~~~~~
    The clientdiag.exe tool does not work on a Windows x64 computer. To fix this
    add the following subkey

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

    The tool will now work and allow you to troubleshoot any problems.

    I tried all the recommendations in this post and many others. None worked
    but this hotfix which was released only 5 days ago did the trick.
     
    Joseph Rinaldi, Aug 4, 2008
    #23
  4. This isn't the same problem that jwchoo has.

    Harry.
     
    Harry Johnston [MVP], Aug 5, 2008
    #24
  5. Hi Harry,

    Are you sure? The problem I was getting was that a few computers were
    appearing in WSUS but getting "This computer has not reported status yet".
    It had been ongoing for about 3 weeks. I installed the hotfix KB954960, and
    then they all started to work.

    jwchoo,

    Can you please try the hotfix and see if it works for you?

    Joseph Rinaldi
     
    Joseph Rinaldi, Aug 5, 2008
    #25
  6. Yes. The superficial symptoms may be the same, but jwchoo's Windows Update log
    shows no evidence of the problem you were having - it's failing at an earlier
    point in the process.
    Well, it won't do any harm, assuming he is running WSUS 3 service pack 1.

    Harry.
     
    Harry Johnston [MVP], Aug 5, 2008
    #26
  7. bzumwalt99

    jwchoo Guest

    Hi Joseph/Harry/David

    I am happy to report I have got it working. Clients are reporting and
    getting updates. The only issue now is they are not populating the
    WSUS Computer Groups as in GP OUs. I followed instructions from
    http://kbalertz.com/920659/Microsof...ces-SelfUpdate-service-automatic-updates.aspx.
    To summarise what I have done:-
    1. check the correct level of permission, ISUR_IISserver user for all
    the relevant folders. and anonynous user is checked on the Default
    Website.
    2. IP address is Unassign for Default website

    Thank for all the help
    Jeremy
     
    jwchoo, Aug 8, 2008
    #27
  8. bzumwalt99

    jwchoo Guest

    I also started WHTTP web proxy service. I am not sure it is necessary.

    Jeremy
     
    jwchoo, Aug 8, 2008
    #28
  9. bzumwalt99

    DaveMills Guest

    Two possibilities:
    1) The client is not being told which group to use in the GPO or the spelling of
    the group does not match that is WSUS console.
    2) The WSUS server is not set to use Client Side Targeting.
     
    DaveMills, Aug 8, 2008
    #29
  10. bzumwalt99

    jwchoo Guest

    Dave

    I have Client side targeting setup. The OUs are nested like
    1. Client systems\XP\Workstations
    2. Client systems\XP\Laptops

    How do I name them in GP ?

    Jeremy
     
    jwchoo, Aug 8, 2008
    #30
  11. bzumwalt99

    DaveMills Guest

    Use the setting in the WSUS policy settings
    Computer\Windows Components\Windows Update\Target group name for this computer

    You can either create a separate GPO for Laptops and Workstations with all the
    setting you need for each.

    or

    Create a GPO for XP with all the settings for all sub OUs and then have other
    GPO for Loptops OU etc which supply just the different settings such as
    groupname etc.

    You decide which, is it easier to have central setting for everything and
    overwrite these with the exception or just have totally separate GPOs and have
    to make change in all if something changes.
    I would definitely have WSUS setting in a GPO or their own and not added to
    Workstation Settings or Laptop Settings. It is too hard to maintain otherwise.
     
    DaveMills, Aug 9, 2008
    #31
  12. bzumwalt99

    jwchoo Guest

    I have done Computer\Windows Components\Windows Update\Target group
    name for this computer
    all the groups but still the same - not populating the groups as the
    ones in Group Policy.

    Jeremy
     
    jwchoo, Aug 12, 2008
    #32
  13. bzumwalt99

    DaveMills Guest

    What does WindowsUpdate.log say the client is getting for "Target Group"
     
    DaveMills, Aug 12, 2008
    #33
  14. I believe you should specify Workstations and Laptops respectively, i.e., ignore
    the nesting entirely and only specify the last component. I may be
    misremembering, I don't do this routinely - but it's worth a try. :)

    Harry.
     
    Harry Johnston [MVP], Aug 14, 2008
    #34
  15. bzumwalt99

    jwchoo Guest

    ok I will give it a try. Thanks
    Jeremy
     
    jwchoo, Aug 18, 2008
    #35
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.