wsus can only see 16 machines

Discussion in 'Update Services' started by fjleon, Oct 3, 2013.

  1. fjleon

    fjleon Guest

    This is really weird, but we have three standalone wsus servers distributed geographically.

    On one branch, the wsus server shows 16 clients , but i have over 30 machines on the branch.

    So, i go to one of them and type wuauclt /detectnow and wuauclt /reportnow.

    That machine appears in the wsus console, but one previosly listed machine now disappears! If i retry with another non listed machine, it appears and the previous one that appeared also dissapears. Repeat and it happens the same.

    This is on win 2008 r2 enterprise and wsus 3.2.7600.256.

    The other two servers have the same wsus version and work fine.
     
    fjleon, Oct 3, 2013
    #1
    1. Advertisements

  2. We saw something similar when our 'cloning' process didn't create a
    new SID on the cloned PC. Drove us crazy for about a week before
    someone cloned a new computer and we watched the entire process.

    Just a thought
    Mike
     
    Special Access, Oct 4, 2013
    #2
    1. Advertisements

  3. fjleon

    fjleon Guest

    We don't clone computers, so sadly this isn't our case.
     
    fjleon, Oct 4, 2013
    #3
  4. If you are using any type of imaging platform, this could be the
    problem. Unless you are building them all from the DVD, then I have
    no more ideas for you.
     
    Special Access, Oct 5, 2013
    #4
  5. fjleon

    fjleon Guest

    The irony is that we use WDS / sysprep on our main branch and it works fine. Machines on the branch with the problem were prepared by normal DVD.

    Since the problem is just with one branch i am guessing there is some network/server issue but i don't know how to properly diagnose.

    Is there some server side log i can check?
     
    fjleon, Oct 9, 2013
    #5
  6. What WSUS version are you running? 3 sp2 (3.2.7600.226 is what I'm
    running)

    You can also check the problem computers and delete the "SusClientID"
    and "SusClientIDValidation" registry values in the key
    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
    and then restart the Automatic Updates service. Then run "wuauclt
    /resetauthorization /detectnow" to have the computer recreate the
    registry entries you just deleted. Then you should see them in the
    WSUS console.

    There is also a client diagnostic tool that you can get from MS
    (http://technet.microsoft.com/en-us/windowsserver/bb466192.aspx, 2nd
    from the bottom) that may help you see if the problem is network,
    computer or WSUS related.

    Good luck!
    Mike
     
    Special Access, Oct 10, 2013
    #6
  7. fjleon

    John Stark Guest

    John Stark, Mar 12, 2014
    #7
    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.