I meant use a script to cancel all distributions. There is a method in
SMS_DistributionPoint called CancelDistribution which could be used to
cancel all in progress distributions.

I don't know of any way to target it based on date the content was pushed,
but you could easily target all in progress content on a single DP.


On Tue, Feb 11, 2014 at 8:33 AM, s kissel <[email protected]> wrote:

> Ryan,
>
> That works in R2, but it's a slow, manual process. There is an easy way to
> remove content from multiple DPs (the messy part if they are currently in
> progress sending), but not really any way to cancel content distribution
> progress to multiple DPs quickly and cleanly from within the console. Also,
> I wouldn't want to cancel all in progress distributions, just most of them.
>
> Regards
> -S
>
> ------------------------------
> Date: Mon, 10 Feb 2014 15:13:29 -0600
>
> Subject: Re: [mssms] A big uh-oh!
> From: [email protected]
> To: [email protected]
>
>
> Under Content Status, if you view status on one of the packages can you
> cancel it?  Or were you saying that is messy?  I can write a script which
> will cancel all in progress distributions.
>
> [image: Inline image 1]
>
>
> On Mon, Feb 10, 2014 at 2:47 PM, s kissel <[email protected]> wrote:
>
> Looking for some ideas to cleanly handle this:
> A script got ran that was supposed to deploy a number of packages to a
> single DP in SCCM 2012. Unfortunately, the script was not thoroughly tested
> and/or was used in a production environment and ended up pushing every
> single package to every single Secondary Site and DP in the environment -
> and this is a lot on a lot!
>
> Fortunately, it twas not I who ran this nonesense, so my hide is safe :)
>
> However, knowing that SCCM can sometimes be temperamental, and having seen
> first-hand how a DP can react when you stop deploying a package that is
> still pushing to it and the WMI traces it can leave behind, is it safer to
> just ride this one out for the next week and a half? Or is there a quick
> and easy way, without getting on SCCM's bad side and ultimately having to
> rebuild sites, to stop the content flow gracefully?
>
> Regards,
> -S
>
>
>
>
>


<<image.png>>

Reply via email to