locked
Computers Not Registering With WSUS RRS feed

  • Question

  • Hi

    i have just replace one of my old WSUS servers with a new WSUS 3.0 server standalone 

    i never transferred the old metadata from the database from the old WSUS server the new one i might add as i wanted a fresh system and new database

    Slowly over the last week machines have been getting detected but its only a small number around 37/100.

    its configured to use Group policy and in the GP settings i have changed the "Microsoft update service location" to the new server

    i have matched the settings between the 2 servers.

    There are 2 GP settings for WSUS one for computers and one for servers, i have created the 2 computer categories on the WSUS server and machines are getting put into there correct group, the issue is its not picking up all the systems on the domain

    any suggestions?

    Many Thanks

    Gordon


    Friday, February 6, 2015 12:31 PM

Answers

  • any suggestions?

    My first guess would be that you've not applied the required patches to your new WSUS v3 server.

    At a minimum that would be KB2734608, but if any of your clients have updated from WU/MU in the last year, then it's more likely that you'll need KB2938066.


    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, February 6, 2015 6:20 PM

All replies

  • Firstly I would confirm that the servers that are not appearing really do have the correct windows update setting by inspecting the relevant registry settings on the affected boxes.

    Secondly WSUS identifies clients based on their ClientID / SusID settings, if your machines were cloned then their ID settings will be identical. Those machines would still get their updates, its just that any time another client with the same ID contacted the WSUS server it would replace the previous entry with the same ID.

    Friday, February 6, 2015 4:01 PM
  • would you suggest i get the database off the old one and transfer it to the new one?

    Friday, February 6, 2015 4:47 PM
  • any suggestions?

    My first guess would be that you've not applied the required patches to your new WSUS v3 server.

    At a minimum that would be KB2734608, but if any of your clients have updated from WU/MU in the last year, then it's more likely that you'll need KB2938066.


    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, February 6, 2015 6:20 PM