Share via

Windows Updates in SCCM - WsusContent size

Ed R 136 Reputation points
2020-12-17T01:55:49.707+00:00

With WSUS, the option "Do not store update files locally" was great because I didn't care to store them, and didn't have enough disk space.
Now I'm getting SCCM set up to distribute Windows Updates, and there does not appear to be an option to avoid storing them locally. Oh well.

I initially chose full installation and express installation files, but changed to just Full when I saw the size of the WsusContent increasing. With only a few Windows 10 Products selected, the size kept growing dramatically over a few days. It's currently at 1.66 TB, and stopped since it's out of room. I've seen other threads about the wsuscontent folder being about 200 GB in size.

Is this normal? What did I do wrong?

48902-0.png

48854-1.png48887-2.png

48911-3.png

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,374 questions
Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
1,073 questions
0 comments
Accepted answer
  1. ESWARARAJU KONETI 2,201 Reputation points
    2020-12-17T12:08:47.117+00:00

    If you have integrated WSUS with ConfigMgr and not using any 3rd party updates, the wsuscontent folder usually contains the metadata only but not the actual executable files (.exe or .msi etc). This folder should not be more than 10GB, in my lab that i have enabled all products with 30 clients for patching, wsuscontent folder is hardly not more than 5GB.

    It looks like you have some automatic approval rules enabled in WSUS options which might be causing the content download.
    Check in WSUS console, options, automatic approval rule. There should not be any rule selected.

    Regards,
    Eswar
    www.eskonr.com
    If the response is helpful, please click "Accept Answer" and upvote it.

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Adam J. Marshall 9,591 Reputation points MVP
    2020-12-17T02:13:13.253+00:00

    200? Mine is about 80-85GB. We also have some customers who have 26GB and 36GB stores but they have it really trimmed down.

    0 comments
  2. Harjit Dhaliwal - MSFT 166 Reputation points Microsoft Employee
    2020-12-17T16:46:12.203+00:00

    Here's a Microsoft Doc to help with maintenance of WSUS/Configmgr SUP.

    0 comments
  3. Fiona Yan-MSFT 2,311 Reputation points
    2020-12-18T08:59:40.247+00:00

    @Ed R

    Thank you for posting in Microsoft Q&A forum.

    1. If we want to run the server cleanup from Powershell, try the cmdlet "Invoke-WsusServerCleanup", it has the same impact as running the Cleanup Wizard from within the WSUS Console application and allows the specification of the same options as parameters.
      Please refer to the following link:
      invoke-wsusservercleanup?view=win10-ps
    2. Also, the following article has several useful scripts including re-indexing the database which should be added into your maintenance plan.
      troubleshoot/mem/configmgr/wsus-maintenance-guide

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.