Have you ever started a package copy job and thought that this was a bad idea at this very moment. It turned out that you actually killed the bad wan link in a remote country and the users there are unable to use the line, because you just started to copy a 3 GB wim file over the wan link. Well to be honest, I did that mistake. But for me, this was after business hours so it did not impact the users. But what I learned from this experience was a method on how to stop the package from copying over the slow link. It is worth to mention that in earlier versions of SMS there was an executable to do just this. It was named stopjob.exe.
The first thing you need to do is to stop the distribution. I started services.msc and stopped the SMS_SITE_COMPONENT_MANAGER and the SMS_EXECUTIVE service. Okay so now you have stopped the distribution. But I know that next time I start these services the copy job will continue and that’s no good…..
So the next thing you need to do is to rename the source folder for the package. Lets say the package source was \serversccm_sources$oswin7. Then you need to rename it to for example \serversccm_sources$osWin7_1 .
What will happen if I start the services now? You guessed it. It will retry as many times as it says in the Site Settings – Component Configuration – Software Distribution:
So if you want this to be done more quickly you could change the number of retries to 1 and delay to 1. So the next time you start the services it will retry 1 time. It is very important to have a look at the distmgr.log while you are doing this. There it will say that the packages has failed eventually. When it is failed you just go into the console and remove the package from the distribution point:
When you have verified that the DP has been removed from the package in the gui under the package – Package status – Package Status – Site you can stop the services and revert the retry settings you did earlier. And last but not least, rename back the source folder.