Disk Full on server after running "Schedule Updates" on OS Image

Question

Looking for advice after filling up our sccm server hard-drive as a result of running a "Schedule Updates" against an OS image
Running SCCM 2012 R2. Site server disk partitioned as 4 drives, with E: drive holding program files, sccm binaries, etc, and G: drive holding all content
At close of play yesterday, I ran the "schedule update" option against one of our OS Images (Win7 Pro x64). When I arrived this moring, I noticed that this had reported a status of "failed" ("failed to find or access the update binaries
to be applied on the image"). I also noticed that our E: drive on the sccm server is now full. There are 2 folder created yesterday which look like they have been created as a result of the Schedule Update:
E:\WSUS\WsusContent - 88Gb
E:\ConfigMgr_OfflineImageServicing - 4.6Gb
Is it ok just to manually delete these folders? Or is there an option within the SCCM console where I can clean up these folders?
Lastly, is there a way to configure the "Schedule Updates" option to point to a specific disk/folder to store and service the offline image, so that this is done on the much bigger G: drive?
Thanks
Stan

Answer 1

Yep. That rule will approve everything and cause everything to be downloaded.
Safe? It's not going to break anything in ConfigMgr if that's your definition of safe here. As mentioned, it's not needed or required by ConfigMgr to deploy updates and having it enabled is useless (as far as ConfigMgr is concerned). Once you disable the
rule, the checkboxes on the advanced tab are irrelevant.
If you leave this rule enabled, yes, your wsuscontent folder will continue to grow.
To reduce its size, you should go and set all approved updates to "Not Approved" and then run the WSUS cleanup Wizard. That will delete nearly all of the update binaries from the WSUSContent folder. As mentioned, EULAs will still exist there but
these are very small size wise so won't be a big deal.
Jason | http://blog.configmgrftw.com | @jasonsandys