WSUS / SCCM 2012 server deletes all downloaded updates after 3 days!?
-
Friday, March 08, 2013 10:11 PMWe have put in place a new Server 2012 running WSUS and SCCM 2012 and everything is working great but after 3 days the server deletes all the update files from the server and I have to run wsusutil reset to have it re-download all the updates again. IT works for a few days then deletes them all over again. I checked and we don't seem to have anything setup to run or clean them up so either there is a glitch or something running to clean these all up after 3 days. Anyone see this before? I tried searching the forums and the web but didn't find anything yet. Thanks in advance!
- Moved by Lawrence GarvinMVP Friday, March 08, 2013 11:54 PM This is a ConfigMgr 2012 SUP question
All Replies
-
Saturday, March 09, 2013 10:05 AMModeratorwhat files are being deleted and does is happen at the exact same time every 3 days?
Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals
-
Saturday, March 09, 2013 3:43 PM
All the updates within the wsuscontent folder is being removed, all 29 gigs of it. I don't know if its the same exact hour its being deleted but its every 3 days. I have to run wsusutil reset in order for it to start downloading all the updates again. I checked in scheduled tasks and nothing in there indicates it is deleting or cleaning up stuff. This is pretty recent in the past week, server has been up for over a month and its just started.
-
Saturday, March 09, 2013 3:56 PMModerator
How did you setup your WSUS? Did you configuration it or let CM12 do it?
WSUS shouldn’t be download anything, only CM12 should be download SU and then only when you tell it to. (ADR still only download on a schedule that you tell it to do.)
http://www.enhansoft.com/
-
Monday, March 11, 2013 8:03 AMI second Garth's statement. It's not needed at all that the SUP (WSUS) does download any *binaries*. A SUP is just used for *scanning* the clients.
Torsten Meringer | http://www.mssccmfaq.de
-
Monday, March 11, 2013 3:30 PM
I am not 100% sure how it was setup, my boss did the initial install since I was busy doing other stuff at the time. From what he tells me, he did everything through SCCM for the setup and has been running the wsusutil reset command to redownload everything that has been deleted after a few days. And sure enough, as of this morning, all the updates have been deleted again right on day 3. Is there a place in SCCM that may have a task running that is deleting them? I haven't seen anything yet but then again its all new to me this past few weeks.
Edit: I did find SITE MAINTAINCE and there is a lot of tasks that look like it deletes files. I am going through there to double check. Could this be an issue?- Edited by JGibbons510 Monday, March 11, 2013 3:34 PM
-
Wednesday, March 20, 2013 10:58 AM
I'm having the same issue
Is there any solution, yet.
What I also noticed. It's quiet possible that we have this issue since installing SP1 for SCCM 2012. I also read that this has some mechanisms to delete expired updates, but from what I could see so far is, that this would just be the case for updates downloaded to SCCM already, not for updates on WSUS.
Even so WSUS should only be used for "scanning" clients, this is not the case in our scenario.
First of all we want WSUS to download all updates and keep them, so SCCM can download the updates from WSUS, when we want to distribute them (which is an option in SCCM), we don't want SCCM to download updates from Microsoft (the internet) directly, as this is taking longer.
Second, we also have systems not managed by SCCM which should use the same WSUS, which is not possible if WSUS doesn'T have the updates anymore.
-
Thursday, March 21, 2013 12:59 AM
First of all we want WSUS to download all updates and keep them, so SCCM can download the updates from WSUS, when we want to distribute them (which is an option in SCCM), we don't want SCCM to download updates from Microsoft (the internet) directly, as this is taking longer.
Hmmm.. this must be a new option on CM2012. I'm not familiar with this option.
Second, we also have systems not managed by SCCM which should use the same WSUS, which is not possible if WSUS doesn'T have the updates anymore.
This, however, is not an option at all. It would require that you "manage" the WSUS server, create Target Groups, issue Update Approvals -- all of which are in direct contravention to the environment in which a Software Update Point is intended to be used by Configuration Manager.
You need two WSUS servers to accomplish this objective. One to act as a SUP for ConfigMgr; the other to act as a standalone WSUS server for the systems not managed by ConfigMgr.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Distribution (2005-2013)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.- Proposed As Answer by Garth JonesMVP, Moderator Saturday, April 20, 2013 2:25 PM
- Marked As Answer by Garth JonesMVP, Moderator Saturday, April 27, 2013 1:39 PM
-
Friday, March 22, 2013 7:05 PM
First of all thank you very much.
Actually we really switched to 2 WSUS servers by now. And for sure it really is at least a lot less confusing where you need to configure which setting.
Maybe just for educational reasons, I would like to add some comments:
Nevertheless we were running our original configuration for quiet some time (serveral years with SCCM 2007 and some months with a complete new installation of SCCM 2012 without SP1) and it worked well.
The option of not having SCCM downloading updates from Microsoft (at the point when you "download" software updates to a deployment package) is for sure not new and existed already in SCCM 2007. You can see this setting for sure the following way (in SCCM 2012):
- You select software updates (which are not already marked as downloaded in SCCM) and click "deploy"
- In the "Deploy Software Updates Wizzard" you specify everything until you get to the step "Download Location"
- In this step you're asked to "Specify the source location for software updates that you will download" and you have the following 2 options:
- "Download software updates from the Internet" -> Which means from the Microsoft Update Servers (as far as I understand)
- "Download software updates from a location on my network" -> This is where we specified the (shared) folder where WSUS locally stores the updates
So this was not a bad option as WSUS downloaded the updates every night (which could take some time) and when we tried to deploy them with SCCM it was pretty fast to download the updates to SCCM.
On the other side all updates which we wanted were stored twice on our servers, so not having the updates on WSUS is an advantage from that point of view. A
Just in case we're for sure not the only ones running SCCM like we did before, as I actually ran in the issue described here before (it was fixed like described there, but maybe caused the "current" issue) http://us.generation-nt.com/answer/fail-download-eula-file-error-0x80244019-help-77391752.html

