locked
System Center - Microsoft Update Catalogue RRS feed

Answers

  • There are other reasons including meta-data refreshes triggered by WSUS itself than can cause this. This has happened a couple of times in the past when Microsoft published updates in a specific way that caused the client to see the catalog as being new.

    Another possibility is that your WSUS server became over-taxed and shut down the WSUS app pool. This in turn causes the clients currently scanning to freak-out and resync the entire catalog. Kent detailed this in a blog post a while back: http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/. In addition to his recommendations, make sure that you've updated all of your clients to the latest WUA.

    Given that your WSUS instance is on your primary site server, how do you know that the traffic spike that you saw was coming from WSUS? Have you reviewed WindowsUpdate.log to find evidence of the catalog being re-downloaded on a client?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, June 7, 2016 7:54 PM

All replies

  • Both of the above will cause clients to completely resynch their WSUS catalogs making deltas irrelevant. Basically, if the WSUS instance a client reports to changes then the client will re-download the catalog. This happens because there's no way for a client to know or reconcile the differences in the catalog on the old instance from that of the catalog on the new instance.

    In both cases that you've noted above, this is exactly what has happened (rebuilding the WSUS database is equivalent to changing the WSUS instance for the reason given).

    Downloading the WSUS catalog is done via BITS though so you could exercise some control on bandwidth. Also, the catalog does *not* come from ConfigMgr, it comes from WSUS. You probably know that but in the above text you say it's coming from the primary which could be misinterpreted by someone else reading this thread and in your case it sounds like the WSUS instance and SUP are co-located with the primary site server and so you used the terms interchangeably.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, June 7, 2016 4:27 PM
  • Thank you for your response, Jason.

    We use a CAS and a Primary. The WSUS is on the CAS and the clients check in with the primary to get the information. 

    Last week neither of the two examples I listed occurred so we don't know why the catalogue was being downloaded.  Any thoughts on what else could occur to cause it? Thanks very much for your feedback.

    Chad

    Tuesday, June 7, 2016 4:48 PM
  • "We use a CAS and a Primary."

    Why? This is a complete waste of a server and simply adds unnecessary overhead and complexity.

    Are you sure you are using a CAS and primary and not just a primary site with multiple site systems.

    "The WSUS is on the CAS and the clients check in with the primary to get the information."

    This is incorrect. The WSUS instance on the CAS is not used by clients. Clients communicate with the SUP/WSUS instance that belongs to the primary site (whether that's on the primary site server or not).

    The reason that the behavior you are seeing occurs is exactly what I said above.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, June 7, 2016 6:12 PM
  • Hi Jason, we do have a CAS and a primary and I agree that it is unnecessary, though this is what I have to work with. Powers greater than myself made that decision. 

    If anyone has any ideas why the clients would be downloading a new catalogue, let me know. The two examples I gave happened years ago. No recent changes have occurred.

    Thanks!

    Tuesday, June 7, 2016 7:09 PM
  • There are other reasons including meta-data refreshes triggered by WSUS itself than can cause this. This has happened a couple of times in the past when Microsoft published updates in a specific way that caused the client to see the catalog as being new.

    Another possibility is that your WSUS server became over-taxed and shut down the WSUS app pool. This in turn causes the clients currently scanning to freak-out and resync the entire catalog. Kent detailed this in a blog post a while back: http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/. In addition to his recommendations, make sure that you've updated all of your clients to the latest WUA.

    Given that your WSUS instance is on your primary site server, how do you know that the traffic spike that you saw was coming from WSUS? Have you reviewed WindowsUpdate.log to find evidence of the catalog being re-downloaded on a client?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, June 7, 2016 7:54 PM