none
WSUS Downstream Syncronization Status

    Question

  • I have 1 primary WSUS servers and 6 downstream servers spread around the globe.  All are running Server 2008 R2.  When I look at the Downstream Servers list in the WSUS console on my primary WSUS server, I see 5 of my downstream servers are fine, but one of them says it has not synchronized in 186 days.  When I go to this server and look at its synchronization history, I see successful synchronizations occurring everyday as scheduled.  Any ideas why the primary thinks this downstream server isn't synchronizing?

    Friday, January 31, 2014 8:29 PM

Answers

  • When I go to this server and look at its synchronization history, I see successful synchronizations occurring everyday as scheduled.  Any ideas why the primary thinks this downstream server isn't synchronizing?

    Most likely reason is a disconnect between the ServerID that the upstream server has and the ServerID that the downstream server has.

    1. DELETE (Unregister?) the Downstream Server from the WSUS console of the upstream server.
    2. DISABLE synchronization on the Downstream Server.
    3. Configure the Downstream Server as an Upstream Server.
    4. Configure the Downstream Server as a Replica Server and redefine the Upstream Server.
    5. Launch a MANUAL synchronization event, and observe the results at the upstream server.
    6. If it works, re-enable automatic synchronization.

    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.

    • Marked as answer by Jay Lay Friday, February 07, 2014 2:47 PM
    Friday, February 07, 2014 12:16 AM
    Moderator

All replies

  • 

    Hi,

    First, check time setting between the two servers, if there is too much differential (in minutes), the reporting rollup will fail.

    Is there any errors in the following log?

    %ProgramFiles%\Update Services\Logfiles\SoftwareDistribution.Log

    Tuesday, February 04, 2014 9:23 AM
    Moderator
  • First, check time setting between the two servers, if there is too much differential (in minutes), the reporting rollup will fail.

    Which should not affect the Last Synchronization Date reported in the Downstream Servers node, because Reporting Rollup has absolutely nothing to do with this data attribute.

    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 07, 2014 12:13 AM
    Moderator
  • When I go to this server and look at its synchronization history, I see successful synchronizations occurring everyday as scheduled.  Any ideas why the primary thinks this downstream server isn't synchronizing?

    Most likely reason is a disconnect between the ServerID that the upstream server has and the ServerID that the downstream server has.

    1. DELETE (Unregister?) the Downstream Server from the WSUS console of the upstream server.
    2. DISABLE synchronization on the Downstream Server.
    3. Configure the Downstream Server as an Upstream Server.
    4. Configure the Downstream Server as a Replica Server and redefine the Upstream Server.
    5. Launch a MANUAL synchronization event, and observe the results at the upstream server.
    6. If it works, re-enable automatic synchronization.

    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.

    • Marked as answer by Jay Lay Friday, February 07, 2014 2:47 PM
    Friday, February 07, 2014 12:16 AM
    Moderator
  • When I go to this server and look at its synchronization history, I see successful synchronizations occurring everyday as scheduled.  Any ideas why the primary thinks this downstream server isn't synchronizing?

    Most likely reason is a disconnect between the ServerID that the upstream server has and the ServerID that the downstream server has.

    1. DELETE (Unregister?) the Downstream Server from the WSUS console of the upstream server.
    2. DISABLE synchronization on the Downstream Server.
    3. Configure the Downstream Server as an Upstream Server.
    4. Configure the Downstream Server as a Replica Server and redefine the Upstream Server.
    5. Launch a MANUAL synchronization event, and observe the results at the upstream server.
    6. If it works, re-enable automatic synchronization.

    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.


    Thanks Lawrence.  Didn't have to go past step 1, the same server was listed twice. Deleting the stale entry solved my problem. *facepalm*
    Friday, February 07, 2014 2:49 PM
  • Thanks Lawrence.  Didn't have to go past step 1, the same server was listed twice. Deleting the stale entry solved my problem. *facepalm*

    :-)

    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.

    Saturday, February 08, 2014 12:12 AM
    Moderator