Not all clients showing up in WSUS

Discussion in 'Update Services' started by Hollie, Aug 29, 2005.

  1. Hollie

    Hollie Guest

    I have a new WSUS server, and 90% of my clients have checked in, but there
    are a few that do not show up. They are installing the updates correctly and
    show the correct AU server name. Is there any way to force them to show up
    in the WSUS console. And why would they be installing the updates, but not
    show up in the console?
     
    Hollie, Aug 29, 2005
    #1
    1. Advertisements

  2. Hollie

    Dave Mills Guest

    Have you set the reporting URL correctly?

    What are your settings? What does the client diag program show. Post
    results from it.
     
    Dave Mills, Aug 30, 2005
    #2
    1. Advertisements

  3. Hollie

    Hollie Guest

    I believe that everything is setup correctly, because I have computers from
    the same OU (and using the same group policy settings) and they have reported
    in. I am just missing a few computers. The computers are recieving the needed
    updates at the scheduled time.

    --------
    WSUS Client Diagnostics Tool

    Checking Machine State
    Checking for admin rights to run tool . . . . . . . . . PASS
    Automatic Updates Service is running. . . . . . . . . . PASS
    Background Intelligent Transfer Service is not running. PASS
    Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
    This version is WSUS 2.0

    Checking AU Settings
    AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
    Option is from Policy settings

    Checking Proxy Configuration
    Checking for winhttp local machine Proxy settings . . . PASS
    Winhttp local machine access type
    <Direct Connection>
    Winhttp local machine Proxy. . . . . . . . . . PASS
    Winhttp local machine ProxyBypass. . . . . . . PASS
    Checking User IE Proxy settings . . . . . . . . . . . . PASS
    User IE Proxy. . . . . . . . . . . . . . . . . PASS
    User IE ProxyByPass. . . . . . . . . . . . . . PASS
    User IE AutoConfig URL Proxy . . . . . . . . . PASS
    User IE AutoDetect
    AutoDetect not in use

    Checking Connection to WSUS/SUS Server
    WUServer = http://WSUSServer
    WUStatusServer = http://WSUSServer
    UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
    Connection to server. . . . . . . . . . . . . . . . . . PASS
    SelfUpdate folder is present. . . . . . . . . . . . . . PASS
     
    Hollie, Aug 30, 2005
    #3
  4. Hollie

    Dave Mills Guest

    Nothing obvious there. Read through the client WindowsUpdate.Log for a
    non reporting client. Last time I did for a failing client it was a
    non SP1 XP system and the log pointed out that WU client not up to
    date enough to self update. A quick visit to MS Windows Update
    installed a more recent client and the self update and reporting
    started to work. The log file can be quite helpful (understatement).
     
    Dave Mills, Aug 30, 2005
    #4
  5. The "client not up to date" is not the issue here, as reported by the CDT
    just used:
    This client is fully updated, and the policies are properly configured and
    applied.

    Your advice to inspect, in detail, the WindowsUpdate.log is the correct next
    step; however, specifically we will want to review the entries near the
    "ReportingWebService" calls, to determine why the client is not /reporting/.
    Since Hollie pointed out that other clients in the same OU with the same GPO
    are working perfectly, the problem must be with individual configurations of
    these clients.

    There are two likely causes of this scenario, based on past observations:

    (1) The clients have a duplicated SusClientID (having been cloned from the
    same system image), and their data is being masked by another system.

    (2) The clients are encountering errors accessing the ReportingWebService
    due to a security issue on the client side (since others can report
    successfully, it is not a server-side fault).

    The WindowsUpdate.log will either confirm that (1) is the most likely cause
    (because Reporting /is/ working correctly at the client), or that (2) is the
    most likely cause, because Reporting is logging errors.
     
    Lawrence Garvin, Aug 30, 2005
    #5
  6. Hollie

    Hollie Guest

    Thank you both for your help. We've found out this was happening due to
    duplicated SusClientId on a group of pc's that all used the same image. We
    have since fixed them and all pc's are reporting as they should.
     
    Hollie, Aug 30, 2005
    #6
  7. Hollie

    Dave Mills Guest

    Thanks, pleased to help.

    Lawrence you hit the nail on the head again. Good call.
     
    Dave Mills, Aug 30, 2005
    #7
  8. Hollie

    dkm Guest

    Hollie,

    How did you correct this problem? I have the same thing going on.
     
    dkm, Sep 1, 2005
    #8
    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.