OSD and installing applications

I am trying to setup an OSD TS that has applications installation as part of it.  Without the applications, I can get it to lay down the wim, add to the domain, install the client, and run updates. 
 
as soon as I add an application installation to the process, it hangs on that application and eventually fails.
 
Any ideas?  I am in HTTPS across my domain.

Try using the continue on error in the task sequence, I had same kind of problems but with that check box thicked I got the task sequence working fine and the application itself was also installed successfully.
 
 

Before I add applications to my task sequence, I always make sure I can successfuly silently install on a client with no issues.  I'd start there and then move into the console.  You should not have to select contiune on error to install an application, sure it may install but may not behave as desired. 

This application is silent, and will install on a client machine outside of OSD, but not within the TS.

I assume you are using RTM code?
I assume you are trying to do the app install AFTER your client installation? Are you running the OSD TS from the same network location (is the content available to the task sequence for the location it is being run from)
Is it all applications, or just a single application that has this behavior?
Can you create a 'synthetic app' that basically sets a registry key and see if that can install via OSD?
Any chance you have a requirement in the deployment type for primary user, but you aren't setting it during the task sequence? Any other requirements that might not evaluate properly during the TS?
 

Is it an application or package you're trying to install?
 
Please provide us with the smsts.log !

Regards,
David
 
view my blog on 
 

Problem solved.  After digging through some logs, I noticed that the system was having trouble connecting to my second DP over ssl.  I checked and forgotten to add a ssl binding when adding the second dp role for IIS.  Applications pull down fine now and everything seems to work.  Guess I overlooked it when letting SCCM install IIS during the DP role setup.