Likely will still end up with a heck-uv-a mess. I actually made that same 
mistake once. :-)

The packages that are in the process of sending and have been removed from the 
DP's will be in a failed state.

________________________________
John Marcum
Lead Desktop Engineer
Bradley Arant Boult Cummings LLP
________________________________

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of David O'Brien
Sent: Tuesday, February 11, 2014 11:47 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] A big uh-oh!

Would this be what you are looking for?

I quickly wrote a script to cancel distribution of Applications or Packages to 
a DP. I didn't have to do too much as I already demoed this script at several 
community events.

http://www.david-obrien.net/2014/02/11/cancel-distribution-content-configmgr-dp/

If you need anything more, just shout ;)

-------
David
http://www.david-obrien.net

________________________________
From: sakis...@outlook.com<mailto:sakis...@outlook.com>
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: RE: [mssms] A big uh-oh!
Date: Tue, 11 Feb 2014 10:14:06 -0600
Yes, it is R2.
________________________________
From: obrien.da...@outlook.com<mailto:obrien.da...@outlook.com>
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: RE: [mssms] A big uh-oh!
Date: Tue, 11 Feb 2014 17:07:46 +0100
It's not R2, right?

-------
David
http://www.david-obrien.net

________________________________
From: sakis...@outlook.com<mailto:sakis...@outlook.com>
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: RE: [mssms] A big uh-oh!
Date: Tue, 11 Feb 2014 10:00:39 -0600
If there is a way to cancel all distributions of a particular package, I could 
run that about 60 times, and that would help us out greatly.
________________________________
Date: Tue, 11 Feb 2014 09:30:28 -0600
Subject: Re: [mssms] A big uh-oh!
From: ryan2...@gmail.com<mailto:ryan2...@gmail.com>
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
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 
<sakis...@outlook.com<mailto:sakis...@outlook.com>> 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: ryan2...@gmail.com<mailto:ryan2...@gmail.com>
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>

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.

[Inline image 1]

On Mon, Feb 10, 2014 at 2:47 PM, s kissel 
<sakis...@outlook.com<mailto:sakis...@outlook.com>> 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










________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.


<<inline: image001.png>>

Reply via email to