Clients don't show up in WSUS but still downloads/installs updates from the server

Discussion in 'Update Services' started by Thomas Olsen, Jun 30, 2006.

  1. Thomas Olsen

    Thomas Olsen Guest

    Hi group

    I have a strange problem with my WSUS installation.

    I have configured a group policy to direct all our clients to the WSUS
    server, but I have noticed that several clients doesn't show up in the
    Computers list.
    I took a look at some of the clients (WindowsUpdate.log) and apparently,
    they get updates from the WSUS server, installs them and reports back the
    result. But still I am not able to see them in the Computers list.

    We were using SUS before on another server but I see in the
    WindowsUpdate.log file that the clients were redirected to the new WSUS
    server.
    The server these clients should show up on is a downstream server getting
    all approvals from its parent server.

    I ran wuauclt.exe /detectnow on one of the clients, but it didn't make a
    difference.

    Below is the part of the WindowsUpdate.log after I ran the command above:

    AU Triggering AU detection through DetectNow API
    1120 624 AU #############
    1120 624 AU ## START ## AU: Search for updates
    1120 624 AU #########
    1120 624 AU <<## SUBMITTED ## AU: Search for updates [CallId =
    {B0D152BC-E635-4C21-BF34-1FCA0E9E6EBA}]
    1120 51c Agent *************
    1120 51c Agent ** START ** Agent: Finding updates [CallerId =
    AutomaticUpdates]
    1120 51c Agent *********
    1120 51c Setup *********** Setup: Checking whether self-update is required
    ***********
    1120 51c Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target
    version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\iuengine.dll:
    target version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target
    version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe:
    target version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wuauclt1.exe:
    target version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl:
    target version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll:
    target version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wuaueng1.dll:
    target version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll:
    target version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target
    version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target
    version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target
    version = 5.8.0.2607, required version = 5.8.0.2607
    1120 51c Setup * IsUpdateRequired = No
    1120 51c PT +++++++++++ PT: Synchronizing server updates +++++++++++
    1120 51c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server
    URL = http://<WSUS server>/ClientWebService/client.asmx
    1120 51c PT Initializing simple targeting cookie, clientId =
    7a5b2573-3e5a-4357-a3c5-ea240e29efd7, target group = , DNS name = <client
    computer name>
    1120 51c PT Server URL =
    http://ams-svc-02.emea.infocus.int/SimpleAuthWebService/SimpleAuth.asmx
    1120 51c Agent * Found 0 updates and 8 categories in search
    1120 51c Agent *********
    1120 51c Agent ** END ** Agent: Finding updates [CallerId =
    AutomaticUpdates]
    1120 51c Agent *************
    1120 51c AU >>## RESUMED ## AU: Search for updates [CallId =
    {B0D152BC-E635-4C21-BF34-1FCA0E9E6EBA}]
    1120 51c AU # 0 updates detected
    1120 51c AU #########
    1120 51c AU ## END ## AU: Search for updates [CallId =
    {B0D152BC-E635-4C21-BF34-1FCA0E9E6EBA}]
    1120 51c AU #############
    1120 51c AU AU setting next detection timeout to 2006-07-01 05:14:55
    1120 51c Report REPORT EVENT: {75E72DC3-0F78-405C-84CA-CB92DD0E955C}
    2006-06-30 12:01:59+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0
    0 AutomaticUpdates Success Software Synchronization Agent has finished
    detecting items.
    1120 51c Report REPORT EVENT: {582B7C88-CA01-4365-9AAF-82FBBA55C9A8}
    2006-06-30 12:01:59+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0
    0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.


    Also from above in the log file, I see that the computer is assigned to the
    Unassigned Computers" group


    Have anyone seen this behavior before?

    Some help is highly appreciated.

    /Thomas O
     
    Thomas Olsen, Jun 30, 2006
    #1
    1. Advertisements

  2. Verify that the client computer has been properly assigned to a target group
    (if using server-side targeting), or that the policy has been properly
    configured and applied (if using client-side targeting), and then run

    'wuauclt /resetauthorization /detectnow'

    to purge the targeting data cookie and allow the client to obtain new target
    group assignments.

    --
    Lawrence Garvin, M.S., MVP-Software Distribution
    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
    And, eveything else is at
    http://wsusinfo.onsitechsolutions.com
    ....
     
    Lawrence Garvin \(MVP\), Jul 1, 2006
    #2
    1. Advertisements

  3. Thomas Olsen

    Thomas Olsen Guest

    Hi Lawrence

    I ran the command you suggested on one of the clients that did not show up
    in the WSUS Computers view, and it appeared in the view. I ran it on another
    computer as well.
    What happened then was that the first computer disappeared from the list and
    the new one was added.

    It looks like I am not able to add more computers to the system, or
    something. I only have 44 computers in the system so far.

    I am running with a remote SQL server database on my system.
    I have verified that I have planty of free disk space and the SUSDB & logs
    are set to automatically grow by 10% with unrestricted file growth.

    Appreciate some help here.

    Thanks.

    /Thomas O
     
    Thomas Olsen, Jul 3, 2006
    #3
  4. This is a classic symptom of duplicate SusClientIDs, most typically caused
    by improperly prepared images that have then been cloned across an
    organization.

    See How do I fix the 'SusClientId' problem?
    at http://wsusinfo.onsitechsolutions.com/articles/025.htm
    for instructions on how to repair this issue.

    --
    Lawrence Garvin, M.S., MVP-Software Distribution
    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
    And, eveything else is at
    http://wsusinfo.onsitechsolutions.com
    ....
     
    Lawrence Garvin \(MVP\), Jul 3, 2006
    #4
  5. Thomas Olsen

    Thomas Olsen Guest

    Hi Lawrence

    Thanks for the information. It looks like you are correct. I followed the
    procedure in the link you sent on some clients, and those clients are now
    reporting back in to WSUS.
    The strange thing is that we have prepared this image exactly the same way
    (using sysprep and Windows minisetup) as for all other computer models, and
    this is the only one we have seen giving this problem.

    /Thomas O
     
    Thomas Olsen, Jul 4, 2006
    #5
  6. The critical key with using sysprep is that you must use the -reseal
    parameter in order to ensure that all unique identifiers (particularly the
    Domain Account SID) are refreshed during the minisetup.

    Generally, it's the changing of the Account Domain SID that triggers the
    reinitialization of the SusClientID. If the Account Domain SID does not get
    changed at initialization (which will be the case if -reseal is not used
    with sysprep), then the SusClientID that was initialized during the building
    of the master image will be reproduced in all of the clones.

    The deletion of the Account Domain SID cached value in the
    ~\CurrentVersion\WindowsUpdate key causes the WUA to sense that it needs to
    reinit the SusClientID, and then does so, along with recaching the current
    Account Domain SID.

    --
    Lawrence Garvin, M.S., MVP-Software Distribution
    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
    And, eveything else is at
    http://wsusinfo.onsitechsolutions.com
    ....
     
    Lawrence Garvin \(MVP\), Jul 4, 2006
    #6
  7. Thomas Olsen

    Thomas Olsen Guest

    Very good feedback Lawrence

    We have procedures covering image building where it is mentioned that we
    need to use reseal with minisetup, but it might be that the person that made
    this specific image forgot to include it during the preparation.

    We will look in to this further.

    Thanks again for your help.

    /Thomas O
     
    Thomas Olsen, Jul 4, 2006
    #7
  8. Thomas Olsen

    Hank Arnold Guest

    An alternate method that works for us is to:

    1) set up the machine
    2) make sure it is out of the domain
    3) stop the AU service
    4) delete the registry WSUS settings
    5) create a ghost image
    6) set up the new workstation from the ghost image (don't reboot)
    7) use Ghost Walker to change the machine name and SID
    8) boot the new workstation
    9) put it in the domain
    10) start the AU service
    11) run WUAUCLT /DETECTNOW

    Our workstations are currently set up with local GP Automatic Update
    settings..... Don't know if this affects the validity of the process

    Regards,
    Hank Arnold
     
    Hank Arnold, Jul 5, 2006
    #8
  9. Thomas Olsen

    Thomas Olsen Guest

    Hi Hank

    Thanks for the tip.

    Since we have seen this problem on one computer model only in our network, I
    think we will redo that particular image for future use.
    I will of course monitor to make sure that we don't have the same problem
    with other computer models as well.

    Thanks.

    /Thomas O
     
    Thomas Olsen, Jul 5, 2006
    #9
  10. And, while this does work, Hank, the point of the whole thread, and several
    others before it, is that there's a critical step missing here that can be
    used to replace your steps 2 through 4, which is the preferred and
    recommended step -- and that is to use 'sysprep -reseal' to prepare the
    image for duplication. :)

    --
    Lawrence Garvin, M.S., MVP-Software Distribution
    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
    And, eveything else is at
    http://wsusinfo.onsitechsolutions.com
    ....
     
    Lawrence Garvin \(MVP\), Jul 5, 2006
    #10
  11. Thomas Olsen

    Hank Arnold Guest

    I agree that there are alternative approaches. We like ours because it
    avoids the necessity of doing a "mini-install". I showed it only as an
    example of another way to accomplish the same thing.

    Regards,
    Hank Arnold
     
    Hank Arnold, Jul 6, 2006
    #11
  12. It's also, "technically", an unsupported methodology for cloning operating
    systems, and Microsoft has published a KB article specifically stating the
    conditions under which they will support a system cloned from an image.

    There are very specific reasons that minisetup runs, and 'working around
    them' doesn't resolve all of those issues. Deleting the WSUS/WUA registry
    keys is but only one issue, and that one isn't even considered by the
    creation of the mini-setup.

    See the following KB articles for more information:

    The Microsoft policy concerning disk duplication of Windows XP installations
    http://support.microsoft.com/kb/314828/en-us

    How To Use the System Preparation Tool (Sysprep.exe) to Perform Disk
    Duplication
    http://support.microsoft.com/kb/298491/en-us

    How to use the Sysprep tool to automate successful deployment of Windows XP
    http://support.microsoft.com/kb/302577/en-us

    How to Disable Mini-Setup Wizard on a Computer on Which You Used Sysprep
    http://support.microsoft.com/kb/287506/en-us

    Best Practices for Using Sysprep with NTFS Volumes
    http://support.microsoft.com/kb/240126/en-us

    HOW TO: Disable the Mini-Setup Wizard on a Windows XP-Based Computer on
    Which You Used Sysprep
    http://support.microsoft.com/kb/321070/en-us

    Known issues that affect program deployment when you use Sysprep
    http://support.microsoft.com/kb/814616/en-us


    --
    Lawrence Garvin, M.S., MVP-Software Distribution Everything you need for
    WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
    And, eveything else is at
    http://wsusinfo.onsitechsolutions.com
    .....
     
    Lawrence Garvin \(MVP\), Jul 8, 2006
    #12
    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.