strtrkn Posted June 25, 2013 Report post Posted June 25, 2013 We're in the process of getting all of our applications into 2012 after moving from 2007. We had a person mistakenly change a package & then autopushed it to ALL of our distribution points (over 90 globally w/ 2 main site servers & 1 cas). This package is over 3gb and now we have a ton of data destroying our pipe as it tries to push out this massive package to all the distribution points. I mainly work on the infrastructure side of sccm, so I'm a bit new to the appdeploy side of the house. What I want to do is kill it. Delete it. I don't care if it's mid-progess; it needs to be stopped now. I've removed the deployment from the collection, but obviously that doesn't stop jobs in progress. I was told in 2007 you could go into the database & delete the job, or delete the actual .job file in the distmgr.box or the schedule.box. I don't know which table in the database that is & I would like it to be a last resort. I also don't know which table it is that was used in 2007. A colleague & I went looking for the job files to delete, but they were all empty (he said in 2007 you could read them in notepad to figure out which was which). Is there anything else we can try? All I can find online is how to delete the actual application or delete from the software update group or remove the application from a collection. I really hope someone here can help me. Thank you for your time. Lindsay Quote Share this post Link to post Share on other sites More sharing options...
