none
Windows 7 computer added to WSUS updates computer group does not appear...

    Question

  • Using WSUS on a Win2k12 server, fully patched etc. etc.

    Added some Win7 computers to it yesterday, they are in the proper AD group for WSUS to know to update them.

    One or more of the Win7 computers don't appear in WSUS...despite being rebooted since yesterday.

    It has not been updated in a long long time...no idea when.

    Must a specific update(s) be run on the PC before it will respond properly to WSUS?? or that WSUS will properly see it??

    I vaguely recall there's some specific per-computer update that must be done for the computer and WSUS to be able to see/talk to each other --  but I don't know what it is -- and I want to know what it is and how I can automagically deploy it to all the 150+ Win7 PCs in our domain...

    Thank you, Tom


    • Edited by tlyczko2 Friday, June 13, 2014 7:25 PM
    Friday, June 13, 2014 3:15 PM

Answers

  • Hi,

    For WSUS 6 and windows 7 clients, no additional update is required. It should be working as long as it is configured properly.

    Step 3: Configure WSUS

    http://technet.microsoft.com/en-us/library/hh852346.aspx

    Worth to notice is that the default port is changed to 8530, so you need specify the port number is GPO.

    In addition, make traffic is not blocked by firewall or proxy servers.

    As referred by Lawrence, to troubleshoot the issue, windowsupdate.log is helpful here.

    Hope this helps.

    Monday, June 16, 2014 7:03 AM
  • I can't just open them up and look at them upon request.

    Then you're up a creek without a paddle.

    I was hoping someone could identify if a particular KB update or something similar must be installed to enable proper communication

    Without knowing the actual STATE of the machine, ANYTHING that we woudl post here would be 100% speculative, at best. I can think of a half-dozen different unrelated possible causes just off the top of my head... any one or all of which might be miles from being correct.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, June 17, 2014 8:15 PM

All replies

  • One or more of the Win7 computers don't appear in WSUS...despite being rebooted since yesterday.

    So what's in the WindowsUpdate.log of one of these Windows 7 systems?

    It has not been updated in a long long time...no idea when.

    So maybe like not since Service Pack 1 came out?


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, June 13, 2014 7:54 PM
  • Unfortunately most of these computers are many miles away from me.

    I can't just open them up and look at them upon request.

    I was hoping someone could identify if a particular KB update or something similar must be installed to enable proper communication -- I have seen mention of such an item but can not recall where I saw it or what it is.

    I will simply document which ones respond and which ones don't, then go from there.

    Thank you, Tom

    Friday, June 13, 2014 7:59 PM
  • Hi,

    For WSUS 6 and windows 7 clients, no additional update is required. It should be working as long as it is configured properly.

    Step 3: Configure WSUS

    http://technet.microsoft.com/en-us/library/hh852346.aspx

    Worth to notice is that the default port is changed to 8530, so you need specify the port number is GPO.

    In addition, make traffic is not blocked by firewall or proxy servers.

    As referred by Lawrence, to troubleshoot the issue, windowsupdate.log is helpful here.

    Hope this helps.

    Monday, June 16, 2014 7:03 AM
  • I can't just open them up and look at them upon request.

    Then you're up a creek without a paddle.

    I was hoping someone could identify if a particular KB update or something similar must be installed to enable proper communication

    Without knowing the actual STATE of the machine, ANYTHING that we woudl post here would be 100% speculative, at best. I can think of a half-dozen different unrelated possible causes just off the top of my head... any one or all of which might be miles from being correct.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, June 17, 2014 8:15 PM
  • Hello,

    Is there any update? I want to confirm if the issue has been resolved.

    If you have any further questions please feel free to let us know.

    Thank you.

    Friday, June 20, 2014 6:08 AM