Hi All

i am having an issue with an application which i have packaged ready to deploiy in the new sccm 2012 sp1

I can deploy my application fine on its own, i have created sccm program sfor 4 sets of drivers which are all msi's, when i chain these as dependencies these are just failing.

Its a test environment and the content is copied manually but the errors are only occuring when the dependencies are attempting to install.

has anyone else come across this

basically i have my 5 applications, 1 collection and the bighand programme has all the others listed as dependencies

can anyone tell me why i would keep getting failed, yet as soon as i remove the dependencies it works fine?


2 Comments   [ - ] Hide Comments


  • I too am having this/similar problem. If we need to use a TS for dependencies to actually work then why the heck am I able to create a dependency right in the application. Makes zero sense. I remove my dependency and then the app just does. totally stupid. I am trying to deploy office and have setup access or the 2010 access runtime as dependencies and the access runtime is set to auto install if neither product is detected. but all my systems are now showing up in the requirements not met tab. NOW when I create a deployment to users that can then install office from the application catalog all works as intended but as soon as I deploy to a workstation with a deadline....nothing works.

    Because of the different languages we are needing a TS is out of the question.

    I have 9 of each:
    access 2010 (language name here)
    accessRT 2010 (language name here)
    office std 2010 (language name here)

    I then have matching ad groups for :
    access 2010 (language name here)
    office 2010 (language name here)

    Then I have the access runtime simply distributed to all the same locations as its matching office language version and set it up as a dependency for office. In theory you deploy office to the workstation, it sees that it needs accessrt and it should simply install it or see that access full version is installed, then install office.

    Could it be the order I have my dependencies setup? I have access as the first check with an or operator to look for accessrt and if not there install it. Access full is not set to auto install.

    Any help from anyone would be GREAT as I need to get this out to over 5,000 systems pretty soon.
  • I know this is an old post but I see 'BigHand' mentioned in the OP and this seems to be the exact issue I am currently having - how to deplot the BigHand client and device drivers in one hit without it all buggering up!

    keane2012 - did you get anywhere with this in the end?
Please log in to comment

Answer this question or Comment on this question for clarity



Try using a Task Sequence instead. When you set dependancies they are hard to troubleshoot.

Answered 01/08/2013 by: Estes
Second Degree Blue Belt

  • I cant use a task sequence its for program deployment and all i want to do is have a series of programs install after each other, not bothered what order
  • I have 5 programs
    i havew a client which must be installed before 4 driver packages
    so i advertise the final driver package which then has a dependency for driver pack 3 which then has a dependency for driver pack 2 and then that has a dependency for driver pack 1 which has a dependency for the client
    but it just fails 1603
    which is content not found?
  • Sorry for the late reply, I've been away. 1603 means the msi failed the install and it could mean multiple things which you can find in the msi log file. I understand that 2012 has improvements but we haven't set up our testing environment yet. Until I do and find out differently I still recommend using a task sequence. If you break up all your application installs in the order desired in each step and if it's setup to use the task sequence progress bar you will see which app it's failing at. At least try creating a TS for testing.
Please log in to comment

You can use a Task Sequence for application deployment - it's not just for OSD builds.

Answered 01/09/2013 by: dunnpy
Red Belt

Please log in to comment

You can see what dependency has failed under deployment monitoring..

Answered 01/09/2013 by: jagadeish
Red Belt

Please log in to comment

Have you tried deploying each application one at a time to pinpoint which application is causing the error? It could be something as simple as the detection method for a particular application causing issues.

Answered 03/18/2013 by: pblopez
White Belt

  • I'd suggest you use the /L*c:\logfilename.log to create a log for each MSI then open those logs with cmtrace to find out what is causing the issues perhaps one of them requires a reboot
Please log in to comment