How to Stop in progress Package Content Distribution to a DP in SCCM Configuration Manager ConfigMgr. Is that possible to cancel ongoing content or package distribution in ConfigMgr? Most of the old ConfigMgr / SCCM admins will say it’s not possible.
However, in reality, this is not true if you’ve SCCM / ConfigMgr. The latest version of SCCM 2012 is R2, and in this version, we can cancel or stop ongoing distribution to a DP.
How to Stop in progress Package Content Distribution to a DP?
This CANCEL package content functionality is useful when a large package is mistakenly distributed to DPs, and the job needs to be canceled to avoid further impact.
From the Distribution Status node in the Monitoring workspace (\Monitoring\Overview\Distribution Status\Content Status – In progress ) of the SCCM / ConfigMgr 2012 R2 console, you can cancel distributions that are in progress to a DP.
Once you click on the cancel (button, as you can see in the above picture) the distribution of a particular package, you will get a confirmation popup with the following message. Click on yes.
The action cancels the distribution job with package ID ‘CAS0016F’ if the distribution is still in progress and might take a long time to complete. Check distrmgr.log or the Monitoring workspace to view the progress. Do you want to continue?
How to Stop in progress Package Content Distribution to a DP in SCCM Configuration Manager ConfigMgr
Once you’ve canceled the distribution of a package, you can see the following entries in the distrmgr.log Found notification for package ‘CAS0016F’
A distribution point has been changed at this site, adding site PRI to the list of sites we are sending package CAS0016F.
A distribution point has been changed at this site, adding site PRI to the list of sites we are sending package CAS0016F.
CDistributionSrcSQL::UpdateAvailableVersion PackageID=CAS0016F, Version=1, Status=2301
STATMSG: ID=2301 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_DISTRIBUTION_MANAGER” SYS=ACNCMCAS01.configmgr.com SITE=CAS PID=4452 TID=4552 GMTDATE=Tue Feb 25 07:01:10.945 2014 ISTR0=”Global – Jan 2014 – Client EN” ISTR1=”CAS0016F” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=1 AID0=400 AVAL0=”CAS0016F”
To know the latest status of the cancellation, Navigate through Monitoring\Overview\Distribution Status\Content Status – Error of the SCCM / ConfigMgr console.
How to Stop in progress Package Content Distribution to a DP in SCCM Configuration Manager ConfigMgr
Once you double-click on the description shown in the above picture, you will get a more detailed popup, and we have successfully canceled the distribution of certain package content.
Package distribution cancelled by user for package “CAS0016F” on Distribution Point “ [“Display=\\ ACNCMPRI01.configmgr.com\”]MSWNET:[“SMS_SITE=PRI”]\\ ACNCMPRI01.configmgr.com \”
Resources
SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)
Author
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…
Hi Anoop,
Do we have any solution for the same in SCCM 2007?
Hello ! – This is not available in SCCM 2007 (if I’m not wrong).
So what happens exactly in the background when we do a cancel ?
What I can understand from the distrmgr log file is:- Distribution manager notifies other components like Scheduler and sender to stop cancel the jobs which are under process. Probably, we need to perform a deep dive into this to get more information. Unfortunately, I didn’t get time to perform this kind of action.
BTW, If you’ve more information on the background process then always welcome to share the same.
Thank you
Anoop
Hi Annop (et al)
Do you know the SCCM2012 application equivalent to the 2007 “disable program”?
Thanks in advance!
sorry to mis-type your name
this option not available in SCCM2012SP1 ! any auto script to stop the in-progress content distribution.
Is there any script to Stop 4000 packages to Single DP.
easy way to stop replication to a single DP – remove the sccm computer account from the local admin group on the dp, wait, your packages will all fail to replicate
Any way in PowerShell to stop a distribution? Not remove the package, just cancel the distribution.
I’m not aware of any. May be you (I could be wrong here – I never tries this) can try to stop server service in DP server to stop the SMB copy of the package?
Stopping server service would cause any impact ?
As one of our dp is not getting content and all packages are going to Inprogress
So I would like to try this step
Use File Replication to set limits – either on Package priority level or bandwidth level. Works perfectly fine
The article above was a bit vague if dealing with multiple site servers as to which instance of the log file to check as opposed to an environment with 1 site server and multiple DPs which may not have the same large number of log files as a site server.
This didn’t work for me. In my case a file was replicating even though it had been removed from distribution to the particular target DP. I redistributed it so I could see it in the In Progress tab to be able to try right click > Cancel but it would just go back to In Progress after showing cancelled by me for a minute or so. It never went to the Error tab.
I could see on the target DP in despoolr.box\receive and on the source (in my case CAS) schedule.log that the content was still sending with no interruption from above activity. I also tried redistributing it again but no difference.
The action that finally got it to cancel was stopping the SMS_EXECUTIVE service on the sending server and deleting the associated .RPG file from the schedule.box\tosend folder (otherwise it was locked by the service) and deleting the .PCK file from the target DP despoolr.box\receive folder.
The PCK file name in the despoolr.box\receive folder can be associated with a package ID/name and remaining transfer progress by checking Send Request entries in schedule.log on the sending server.
The RPG file name in the schedule.box\tosend folder can be associated with a package ID/name and remaining transfer progress by matching the JobID of a Send Request in schedule.log on sending server.
If these details don’t show in the log it’s possible a file or files could be stale e.g. if the disk filled up. I’m not sure if they get cleaned up in that instance. Also if the file is huge like in my case it may be obvious which file is related to the errant replication activity 🙂
P.S. Please delete this comment as a double post – slight correction in the more recent version below.
Excellent!