SCCM 2012R2 CU2 Single Primary with multiple secondaries Single upstream WSUS/SUS server at the Primary Multiple downstream SUS servers at the secondaries
Noticing over time that clients at secondary sites are slowly repointing to the upstream server, and causing bandwidth issues as it's pulling update scan metadata from this WSUS. It also seems that it may be pulling updates directly from the WSUS server itself and not from the SUP and not from the DP. Does anyone know how to repoint the SCCM clients back to their local SUP and not failover to the upstream server? What I have done in the past is stop the WSUSPOOL on the upstream server. This will result in the SCCM client timing out and reverted back to the local WSUS. But once I restart the WSUSPOOL, SCCM clients start to slowly repoint to the upstream server. Really frustrating. Also why would an SCCM client pull directly from a SUP [WSUS] and not from the DP? The only thing I believe I can do is use SCCM to update the registry settings based on boundary collections to ensure that it doesn't change the settings. I'm loath to use GPOs as we may inadvertently repoint a client that is no longer located in the appropriate location OU. Ideas anyone? George
