This question is continuing from my previous question where I had set maintenance windows once the deployment was done(we only had 6 years worth of updates to deploy!!)
I did not want the updates to run during work hours 8 am to 6 pm on any weekday.
I had deleted the entries with Updates management and forced a machine policy retrieval and evaluation cycle on each of the 5000 + devices.
I also disabled the software updates client agent on the primary server just to make sure the updates dont get deployed.
Yesterday evening i setup the new deployment with the required maintenance windows in place (weekday 6pm to 6am, weekend Fri 6pm to Mon 6 am)
Everything was fine till this morning when once of the sites (having a 10MB line and already running at 90% capacity) reported very heavy inbound traffic from the primary SCCM server.
I checked a few devices on this site/subnet and the maintenance window had taken effect (updates stopped at 6 am this morning)
However the inbound traffic was persistent to this location and finally we had to stop IIS on the primary server and the 2 secondary servers closer to this site.
We have at least 100 other sites to which updates were deployed and the above maintenance windows set. None of the other sites reported any issues (or they might have had a bigger pipe and hadnt noticed the rise in traffic)
My question is what else might be causing this rise in traffic from the primary SCCM server (other than updates). Please let me know the log files that I can check to get this information.
I have checked and there is no other software deployment or major SCCM activity targeted at this site.
IIS is now turned on and the spurge in traffic was immediately evident. Is there any way we can stop updates deployment other than disabling IIS?
Any help in this will be greatly appreciated