SCCM 2007 - Application deployment failed to some computers

Posted on 2009-12-21
Last Modified: 2013-11-21
I just deployed a task sequence to 65 computers which was just supposed to uninstall an application and then reinstall the application from the new location.  It worked fine on 40 of the computers.  I am left now with 25 failed installations.  I believe there was a problem on the first install and the program was not installed properly to begin with and I think this caused step 1 of the task sequence to fail which was the uninstall.

I have two questions here...

1) If the uninstall step fails in the task sequence, would it not even go on to the next step?  If I had selected Continue on Error, would it just have moved on?

2) Now that I have this problem, how can I just set the application to install on this subset of 25 computers easily?

Thank you!
Question by:mattpayne59
    LVL 2

    Expert Comment

    1.  If you would have selected "Continue on error" on the Options tab of the individual task it would have continue to the next step (i.e. just moved on).

    2.  You can create a Collection that has a Membership rule that queries Add/Remove programs for the re-installed application by Name and Install Date.  If the newly installed application is not distinguishable based on these criteria then it might be a little more cumbersome.  You might have to export a list of the Failed computers and create a Collection with a Membership rule that only includes those Computer Names.

    Author Comment

    How do I create the collection based on whether or not a program is in Add/Remove Programs?  On the ones where it failed, the program is not installed at all.
    LVL 2

    Accepted Solution

    1.  Under Collections, Rt-Click on a node and select New > Collection
    2.  Name the Collection and hit the Next button.
    3.  In the Membership Rules sections click the Query Rule button (i.e. the yellow one).
    4.  Name the Query Rule and hit the Edit Query Statement button making sure that the Resource class equals System Resource which it is by default.
    5.  Click the Criteria tab
    6.  Click the Criterion Properties button which is the yellow-star
    7.  See the image below for the correct entries.
    8.  The value will be the name of the application.  In your case, you will probably use an "is not equal" or "is not like" conditional filter instead.

    Featured Post

    Too many email signature updates to deal with?

    Are you constantly visiting users’ desks making changes to email signatures? Feel like it’s taking up all of your time? Wish you could manage all signatures from one central location, easily design them and deploy them quickly to users? Well, there is an easy way!

    Join & Write a Comment

    Consider a situation when you deploy a seemingly harmless software package to your network without testing and therefore without fully knowing the implications of your actions. I was recently involved in just this situation when a corporate IT netwo…
    Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …
    In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
    This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

    754 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now