locked
What should be in the WSUS Content folder....if anything?? RRS feed

  • Question

  • Ok, I'm a little confused about this...

    I have a central site (WSUS upstream), 4 primaries (WSUS autonomous downstreams), and 100+ secondaries (WSUS replicas).  If my data source for all my update deployment packages is a share on one of my primaries (packages$), why do I even need a WSUS content folder on all my wsus servers?  By doing some significant WSUS cleanup, I reduced my WSUS content folders from 100+GB to about 2GB, but do I even need it at all??

    Especially on the replicas - why would I need a WSUS Content folder on these?

    If I install (or reinstall) WSUS, shouldn't I just select to not store updates locally, given my configuration?

    Thanks for clearing this up!


    xtiyu32n
    Tuesday, March 2, 2010 6:53 PM

Answers

  • My question still remains....with SCCM, why would I ever need ANY update files stored in my WSUS Content folder??  If I download my updates (via SCCM) to a Packages$ share, my WSUS Content folder should be virtually empty, right?

    xtiyu32n
    Thursday, March 4, 2010 3:35 PM
  • Yes that is correct, all it really contains is license agreements and such for different updates.... no actual update content is stored in that folder.
    • Proposed as answer by BigPappaJ Thursday, March 4, 2010 5:38 PM
    • Marked as answer by Robinson Zhang Monday, April 5, 2010 7:24 AM
    Thursday, March 4, 2010 3:59 PM

All replies

  • When using SCCM to handle updates... the WSUS directory has the software update share in it where the updates are stored locally when you download them to Update lists or deployments.  The WSUSContent folder under WSUS seems to contain txt files for updates and manyof mine are in different languages... seeing as these aren't .ini or .inf files.. they shouldn't be referenced or needed by the individual updates.  I'm not sure that this helps much but its more info if nothing else.
    Wednesday, March 3, 2010 8:06 PM
  • So, couldn't I NOT check "store updates locally" when I install a new WSUS server in my environment, since the files will be stored in the data store I specify in SCCM (Packages$)?


    xtiyu32n
    Wednesday, March 3, 2010 8:57 PM
  • Yes I believe that is correct.  The updates are stored in the packages you create when creating deployments under C:\WSUS\UpdateServicesPackages.
    Wednesday, March 3, 2010 9:39 PM
  • If you do not want to cost more space on this folder , hope following link can help you:

    What to do when your WSUSContent folder grows too large
    http://blogs.technet.com/gborger/archive/2009/02/27/what-to-do-when-your-wsuscontent-folder-grows-too-large.aspx

    Thanks.
    Thursday, March 4, 2010 7:19 AM
  • My question still remains....with SCCM, why would I ever need ANY update files stored in my WSUS Content folder??  If I download my updates (via SCCM) to a Packages$ share, my WSUS Content folder should be virtually empty, right?

    xtiyu32n
    Thursday, March 4, 2010 3:35 PM
  • Yes that is correct, all it really contains is license agreements and such for different updates.... no actual update content is stored in that folder.
    • Proposed as answer by BigPappaJ Thursday, March 4, 2010 5:38 PM
    • Marked as answer by Robinson Zhang Monday, April 5, 2010 7:24 AM
    Thursday, March 4, 2010 3:59 PM
  • Yes, that's what I thought.  Thanks!


    xtiyu32n
    Thursday, March 4, 2010 5:08 PM