• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 742
  • Last Modified:

SCCM 2007 - Application deployment failed to some computers

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!
0
mattpayne59
Asked:
mattpayne59
  • 2
1 Solution
 
CitySecCommented:
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.
0
 
mattpayne59Author Commented:
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.
0
 
CitySecCommented:
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.
NewCollectionWizard-QueryBased.png
SCCM-CriterionProperties.png
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now