1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WSUS clients not registering

Discussion in 'Software' started by SimonV, Sep 4, 2006.

  1. SimonV

    SimonV Petabyte Poster Administrator

    6,616
    149
    228
    I have 100 new workstations that are not registering their information with WSUS, they are picking up updates and installing them as normal but the WSUS admin panel only shows 1 PC from the 100 getting updates.

    I'm pretty tied up with other stuff this week so I thought I'd get some ideas from you guys for when I get the time to look into this later.
     
    Certifications: MOS Master 2003, CompTIA A+, MCSA:M, MCSE
    WIP: Keeping CF Alive...
  2. AJ

    AJ Administrator Administrator

    6,771
    102
    221
    Si, where the new pc's imaged using ghost?

    If so check HERE as there seems to be some issue with ghost and WSUS.

    HTH :biggrin
     
    Certifications: MCSE, MCSA (messaging), ITIL Foundation v3
    WIP: Looking at doing ..................
  3. SimonV

    SimonV Petabyte Poster Administrator

    6,616
    149
    228
    Yes imaged using ghost, that could be the answer. I've got 10 mins so I'll try those registry edits and let you know.
     
    Certifications: MOS Master 2003, CompTIA A+, MCSA:M, MCSE
    WIP: Keeping CF Alive...
  4. SimonV

    SimonV Petabyte Poster Administrator

    6,616
    149
    228
    This seemed to do the trick, there were only two of the entires "AccountDomainSid" &"SusClientId" that needed to be deleted, I'll create a script that deletes these entries and set that as a startup script in GP.

     
    Certifications: MOS Master 2003, CompTIA A+, MCSA:M, MCSE
    WIP: Keeping CF Alive...
  5. SimonV

    SimonV Petabyte Poster Administrator

    6,616
    149
    228
    For anyone thats interested I created a script to delete the above reg entires then added the script as a startup script in group policy, heres the script I used:

    Code:
    Const HKEY_LOCAL_MACHINE = &H80000002
    
    strComputer = "."
     
    Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _ 
        strComputer & "\root\default:StdRegProv")
     
    strKeyPath = "SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"
    strDWORDValueName = "AccountDomainSid"
    strBinaryValueName = "SusClientId"
     
    oReg.DeleteValue HKEY_LOCAL_MACHINE,strKeyPath,strDWORDValueName
    oReg.DeleteValue HKEY_LOCAL_MACHINE,strKeyPath,strBinaryValueName
     
    Certifications: MOS Master 2003, CompTIA A+, MCSA:M, MCSE
    WIP: Keeping CF Alive...
  6. Bluerinse
    Honorary Member

    Bluerinse Exabyte Poster

    8,871
    167
    256
    Why you no use a da Sysprep to prepare de image for clone without duplicate SID :ohmy

    Nice script though Si.

    WSUS is cool 8)
     
    Certifications: C&G Electronics - MCSA (W2K) MCSE (W2K)
  7. simongrahamuk
    Honorary Member

    simongrahamuk Hmmmmmmm?

    6,199
    125
    199
    I had a number of issues with WSUS, and although I have to admit that it is cool, I never found the time to troubleshoot those issues, and ended up removing it from my network.

    Since I Re-image all of the clients every 14 weeks I simply turned off Auto Updates and do them manually for the new Image. 8)
     

Share This Page

Loading...