WSUS only registeres a fix number of clients (not specific clients

Discussion in 'Update Services' started by JeffG, Jul 21, 2005.

  1. JeffG

    JeffG Guest

    If these clients are deployed via imaging of some sort, and it sounds
    as if they are, search the group for error resolution for imaged
    machines.
    JeffG

    On Thu, 21 Jul 2005 05:07:04 -0700, "Ortwin Ebhardt" <Ortwin
     
    JeffG, Jul 21, 2005
    #1
    1. Advertisements

  2. We have recently updated form SUS to WSUS. Our WSUS-Server only registeres 12
    Clients (of aproximative 200). At least he shows only 12 clients. This
    clients are not specific (meaning, they change, see below).

    In fact, on computers not shown on the WSUS-Console updates ARE dpeloyed
    from the WSUS-Server. Sometimes those Computers are even shown in the
    WSUS-Console, while some other client disapears instead.

    Three of the registered clients are servers. They are not droped. nine are
    workstations, of which some are droped and some not. We couldn't make out a
    pattern.

    Is there any known limit regarding Soft- or hardware-versions?

    To our system:
    We don't use ActiveDirectory (workin in a Novell DNS instead), SUS was
    enabled with registry-keys (deployed by NAL-Objects). All Clients use Windows
    XP SP2. Our WSUS-Server is on Windows 2003 Server with SP1.
    Our clients get their IP-Address via DHCP. Our servers have fixed ones.
    There is no firewall between the WSUS-Server and the clients.

    Would be great, if anyone had ANY idea...
     
    Ortwin Ebhardt, Jul 21, 2005
    #2
    1. Advertisements

  3. Hi,

    You haven't by any chance for those computers used an image where the
    source for the image has been in contact with an SUS or WSUS server?

    If a source computer for an image is connected to a WSUS server, before
    you create the image, to avoid problems, you must under the registry key
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

    delete the following values:

    AccountDomainSid
    PingID
    SusClientId


    On the computers you already have running, you need to delete the
    same 3 registry values listed above.

    Then you should stop and start the Automatic Updates service
    and then run the following command:

    %SystemRoot%\system32\wuauclt.exe /resetauthorization /detectnow


    For a VBScript that does this, see post in this link:
    http://groups.google.co.uk/group/mi...pdate/msg/88c6e4e5317f24c9?dmode=source&hl=en
     
    Torgeir Bakken \(MVP\), Jul 21, 2005
    #3
    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.