We're using SCCM 2012 and I'm packaging all of our application and testing them as I go. Some only have .exe's and are more difficult than the .msi's. Some have no documentation and I'm trying different types of command line switches to see what works.

The only way I am able to test these out is create the application, deployment type, and deployment and then push it down to a test client I have.

When an application downloads and then immediately fails, which logs can I review for more information? Looking at client logs for SCNotify, Execmgr, and Windows\CCM\Logs doesn't reveal much. The server side logs don't appear to shed any additional light either.

I'm not doing a task sequence so SMSTS.Log isn't much help.

Where do you guys begin troubleshooting when you think you have the correct command line but the application downloads to client and then fails?


0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



Before you install the application from SCCM you should test that it is actually working fine in system context. You can run a command prompt in System context through PSEXEC tool. Search for it and you will get all the details.

If the application does not work fine then it needs to be repackaged again. and if it works fine, it should work throught SCCM as well if you have not created a mess while creating an application. :)






Answered 08/15/2013 by: piyushnasa
Red Belt

Please log in to comment