SCCM: Forcing a Task Sequence to Rerun

There are well known methods to force an advertisement to rerun – including several add-on tools available for the SMS or SCCM console.  To date, however, there are not equivalent methods to force a task sequence to rerun.  Part of this may be because task sequences are typically thought of as focused on Operating System Deployment (OSD) and rerunning these types of distributions are not as common as rerunning advertisements.

While task sequences are the best solution out there for OS Deployments they are much more flexible than just that – including distributing software in very complex scenarios including support of dynamic decisions during execution, handling reboots, enabling specific sequencing of application deployment, etc.  With this kind of power many organizations are using task sequences for software deployment and the ability to force a sequence to rerun on a selective basis and without having to manually logon to individual clients is crucial.  The process to make this happen is very easy.

First, identify your task sequence by ID.  My test sequence is CEN00027.







Note that in my lab this sequence has already run in the past.

The advertisement for the sequence is set with a mandatory execution time – which resulted in the first run.  No other mandatory times have been added.  Further, the advertisement is set to allow rerunning.  If you had an advertisement set to not rerun you should be able to force it to rerun but this would likel require additional WMI and registry edits.  I haven’t tested that specific scenario.

From here, open WMI on the client system of interest and connect to the root\ccm\scheduler namespace.
Click ‘Enum Classes’, select Recursive and then scroll to the bottom and double click on CCM_Scheduler_History() and then click instances.
In the list that shows up, find the entry that corresponds to your task sequence ID and delete it.
With the deletion made, restart the SMS Agent Host service (CCMExec) on the target client.
In a few minutes, the program balloon will pop up indicating the sequence is about to run again.
The process described is manual but could be automated if desired. 

Comments (9)
  1. Sam says:

    nice job describing the steps to rerun a program, but am i the only one on earth that thinks SCCM is really more complicated than it should be?  i mean all i want to do is deploy a package on computers!

    we spent countless hours and money setting up an SCCM infrastructure, and it causes us more pain than when we used GPOs and startt batch files….

  2. steverac says:

    Thanks and sorry you are having issues ith SCCM.  Contact me by email and I'd be happy to discuss your concerns with you.

  3. Nick says:

    Sam is correct. Especially when you add MDT into the mix.

  4. Jess says:

    Is there a way to run a task sequence without advertising it? Our environment are having a duplicated guids so we stopped the advertisement.

  5. steverac says:

    No, the TS has to be advertised.  Hopefully you are working to get the duplicate GUID's cleaned up.  Having GUID uniqueness is critical to proper functioning of SCCM on every level – not just advetisements.

  6. M. Holt says:

    I second that SAM! I’m sure we’ve all spent countless hours troubleshooting vague error codes and digging into forums for answers. So often I can push out an application but get a percentage of workstations that generate some unexplainable error.  

  7. E. Dergo says:

    I agree with Sam,   The turnaround time between updating a Task Sequence and seeing if it works is a huge time burner.    I fail to understand why a TS needs to be advertised to workstation to try it.  It would be a lot nicers if we can run it manually like we do with a package.

  8. mk-fin says:

    Thanks for your great advice! I had really hard time to re-run software installation to sub-domain machines (couldn´t do it with Right Click Tools. In main domain it works fine). I took remote control over those few broblem-machines and followed your instructions. Got installation fineshed fine!

  9. Anshul says:

    I have the following in an UpdateDeployment.log

    Install not allow as another job is still in progress. UpdatesDeploymentAgent

    This assignment ({ID}) will be retried once the current installation completes. UpdatesDeploymentAgent

    Can i use the same technique to get rid of messages for the  Deployment again and install it ?

    Removing information about the deployment from rootccmsoftwareupdatesdeploymentagent does not help.

Comments are closed.

Skip to main content