Sync Software Updates causes clients to flood network
do you have SUP installed on the secondary sites??
If you have only one SUP on primary, the clients will reach out primary for the catalogue. You need to have secondary SUP on the secondary sites so the clients can get the catalogue form there rather going to the primary.
August 19th, 2015 6:37am
We have a Config Man 2012 CU4 environment with 1 CAS, 1 Pri and some secondaries and quite a few DP's.
The issue is that when we sync Software updates it seems to trigger the clients to check in with the PRIMARY all at once with 40-60MB sync files for each machine all at once. This times 1000's of machines kills the bandwidth of the network as everything
is hitting the Primary.
We have looked around to try and determine why and what causes this with little luck. This just started happening in the last couple months.
August 19th, 2015 5:35pm
Check out http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/
August 19th, 2015 7:27pm
We have increased the pool size as the article suggested prior to these issues occurring to address the pool crashing... this has worked for the crash issue but not the issue I posted above. We also run the cleanup tool but may need to defrag more often.
We will try that and post the results of our findings.
August 19th, 2015 9:49pm
We have a Config Man 2012 CU4 environment with 1 CAS, 1 Pri and some secondaries and quite a few DP's.
Just being curious: why is there a CAS if there is just one primary site?
August 20th, 2015 1:42am
Would a cleanup of the wsus database cause the client to pull a full policy download? it seems it should only be synced around 5-8MB instead of 40-60MB ... we will consider the SECONDARY SUP install but the question remains is that the default size
of the patching policy when refreshing? Isn't the default much lower?
August 21st, 2015 12:42pm
We have a Config Man 2012 CU4 environment with 1 CAS, 1 Pri and some secondaries and quite a few DP's.
Just being curious: why is there a CAS if there is just one pri
August 21st, 2015 12:42pm
Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?
No, Cleaning up the WSUS db, should not cause a full sync to occur.
August 29th, 2015 1:23pm
Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?
No, Cleaning up the WSUS db, should not cause a full sync to oc
August 29th, 2015 10:44pm
So we have been able to replicate the issue by Syncing for this months patches today. Upon completion of the sync and the update info syncing to the Primary, clients begin to flood the network with ~65-75 MB files requesting update info.
The issue does not happen during the scheduled 24hr SCCM/WSUS syncs to Windows Update.
WSUS maintenance / cleanup was done earlier in AM.
September 8th, 2015 9:19pm
It sound like it is time for you to call Microsoft Support (CSS), they will work with your on this issue.
September 9th, 2015 8:53am