How to Stop SCCM Deployments with Immediate Effect

How to Stop SCCM Deployments with Immediate Effect? In a real-time scenario, I have faced several instances of those we need to stop the advertisement immediately to decrease impact to the client machines. Today, I have gone through a good write-up on this topic from Shaun Cassells. How to stop SCCM Advertisements with immediate effects? Here you go!

All credits to Shaun Cassells for this post, and he has some more tips in the latest post here.

Read the original post here ( Some problem with this MyITForum post)

Scenario: An advertisement went out for a package that is causing havoc. Let’s say it is rebooting servers and workstations.   How do you stop it NOW!?!?!  With a Big Red Stop Button (BRSB).

Patch My PC
How to Stop SCCM Deployments with Immediate Effect
How to Stop SCCM Deployments with Immediate Effect

How to Stop SCCM Deployments

Below are five scenarios with varying speeds and success rates.

Method 1: Stop the IIS service or the SMS_OFFER_MANAGER service on all servers. 

Upside: Everything stops

Downside: Everything stops, including normal client communications or any other distribution


Method 2: Delete the source package files of the DP(s) update: change the NTFS folder permissions to deny any client from reading the source files.  Thanks, jnelson.

Upside: All clients trying to run errant advertisements will say “Waiting For Content.”

Downside: Copying the package source back to the DP after everything calms down.

Method 3: Delete the Advertisement (Do not do this)

Upside: It makes you feel better

Downside: This does not stop any clients until a policy refresh is triggered.  You also lose all tracking of the damage you have wrought.

Method 4: Disable the Program

Upside: Prevents further execution

Downside: This does not stop any clients until a policy refresh is triggered.

Method 5: Expire the advertisement

Upside: Prevents further execution

Downside: This does not stop any clients until a policy refresh is triggered.

Summary: The best solution for Big Red Stop Button (BRSB) appears to be Method 2.  Delete the files of the DP.  You will need to know the PackageID. (see reports below) and the location of the DPs (see reports below).  

The best order of execution to achieve BRSB

  1. Identify PackageID
    1. See report below
    2. See console command line below
  2. Identify DPs that you will need to target
    1. See report below
  3. Run a script to delete the files off the DPs
  4. Disable the program
  5. Disable the advertisement (change the execution expiration time)
  6. View reports on advertisement success rate so you know who to go fix

If I desire to post the scripts or more screenshots on how to do this, please respond to this post, and I’ll whip more docs up. 

The clients have received new policies to prevent the errant program from executing again now that the package has stopped.  How do I get the files back on the DP?  Easy, refresh the Distribution Points from the package.  Refresh will keep the DP version the same.  Reminder: if you update the DPs.  You will be creating a new version, which may cause clients to execute this new package.  (Been there)

Helpful Reports (SMS 2003)

List of All packages:


List of All Active Package Distributions:


List of All DPs:


Location of DP (SMS 2003)


How to add NodeInfo to the SMS 2003 console? 

Add the following switch to the console command line

/SMS:NodeInfo=1 or /SMS:NodeInfo=2

Adds a property sheet that contains node information such as the GUID, WMI instance data, and the named values associated with the node to a node’s property page. You access the node information sheet by selecting the Node Information tab. Typically, you use this option to develop or debug extension snap-ins that extend the SMS Administrator console.

This option can be set to 1 or 2. I am putting NodeInfo to 1 place the Node Information sheet last on the property page. Setting NodeInfo to 2 places the Node Information sheet first on the property page.

SMS 2003 command line:

C:\smsadmin\bin\i386\sms.msc /SMS:NodeInfo=1

SCCM 2007 commandline

“C:\Program Files\Microsoft Configuration Manager Console\AdminUI\bin\adminconsole.msc” sms:debugview=1

How to stop advertisements with immediate effect.


3 thoughts on “How to Stop SCCM Deployments with Immediate Effect”

  1. Hello Anoop,

    Excellent post again 🙂
    Using Method 2 place all the clients on “Waiting for content”. SO if it is just a delay I need to push the package it is fine, but if it is a real cancellation I want, meaning the package will not be push anymore, what would be the solution to clear all this “Waiting for content” ?

  2. Hello Anoop,

    I will add we have some packages which are published to the wrong collection for example, so Method 2 applied but if I want to reissue the same distribution to the correct collection what will be the best way to do so?
    For now Method 2 and then create entirely new advertisement… with changing the location of the packages, is it correct?


  3. Hi Felymich,

    The second method is to clear the content of the package, once you verify that the wrong adverts did not create any harm though reports you can simply delete the advert and re add the content to the DP’s and deploy it the right collection this time.


Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.