Applications Do Not Deploy To Server 2008 R2 During Task Sequence - Execution status received: 2 (Application is not required on the client )


  • Hi All,

    I'm having an issue when deploying any application during the task sequence for Server 2008 R2 Standard using SCCM 2012 RTM.  The same applications work fine when deployed during TS to Windows 7.  The SMSTS.log file indicates that the application is not required:

    Passed in version 7 for ScopeId_489F0D05-6A03-4538-8833-F074B3AAABC5/RequiredApplication_004e85eb-7a88-4c76-b8fc-766e5e00a515	DCMAgent	12/12/2013 6:17:11 PM	1084 (0x043C)
    CAppMgmtSDK::GetEvaluationState ScopeId_489F0D05-6A03-4538-8833-F074B3AAABC5/RequiredApplication_004e85eb-7a88-4c76-b8fc-766e5e00a515.7 = NotRequired	DCMAgent	12/12/2013 6:17:11 PM	1084 (0x043C)
    NotifyProgress received: 2 (Application is not required on the client )	InstallApplication	12/12/2013 6:17:11 PM	1084 (0x043C)
    Installation job completed with exit code 0x00000000	InstallApplication	12/12/2013 6:17:12 PM	1520 (0x05F0)
    Execution status received: 2 (Application is not required on the client )	InstallApplication	12/12/2013 6:17:12 PM	1520 (0x05F0)
    Install successful	InstallApplication	12/12/2013 6:17:12 PM	1520 (0x05F0)


    I've checked the following:

    • Application Requirements are correct.  The same thing happens with correct OS requirements or with no requirements.
    • The applications CAN be deployed via SCCM after the Task Sequence to the system
    • The package is set to allow install during TS without advertisement

    The strange thing is that the application deployments worked fine during Build/Capture.

    Any guidance would be greatly appreciated.

    Tuesday, December 17, 2013 6:43 PM

All replies

  • Is this an application or package? I wanted to clarify what you have there.

    Can you post AppEnforce.log if this is an app and execmgr.log if this is a package?

    Tuesday, December 17, 2013 7:05 PM
  • Sorry - I incorrectly used package in the third bullet - this is in relation to applications.  Packages work just fine and I can actually convert the applications into packages and they deploy fine during the TS - however I think that is just a bandaid to a bigger problem.

    The AppEnforce.log file contains nothing because the task sequence doesn't believe the application should be installed.

    Tuesday, December 17, 2013 7:09 PM
  • Have you already examined AppDiscovery.log, AppIntentEval.log and other related logs (ci / dcm ones)?

    Torsten Meringer |

    Tuesday, December 17, 2013 7:20 PM
  • I seem to be missing those logs from my capture - it'll take about 30 minutes to recreate them, but I'll post the useful info here as soon as I have new logs.
    Tuesday, December 17, 2013 7:29 PM
  • Okay - I've recreated the logs and attached them here (please ignore the errors for the ***PAUSE*** step - it's merely a way for me to kill the TS before letting it run too far) - anything from 12/2 is likely from the build/capture:

    Upon initial inspection I see a status 16 on the Nuance PDF Converter (failed to evaluate), but again there is no AppEnforce log so I know that it's not even getting to the execution phase.  I get a few DCM Agent failed to start up and a couple CI Agent failed to start up.  I'm not totally familiar with these logs so I'm not sure what I should be looking for - I'm much better at reading the SMSTS log, but so far Execution Status 2 has proved to be something hard to find on google :)

    Tuesday, December 17, 2013 8:43 PM
  • Can you check one more thing.

    What is your setting on application under Content tab, very bottom (Deployment Options).

    Tuesday, December 17, 2013 8:45 PM
  • It's set to "Do not download content"

    However, this particular system is located in a non-slow/unreliable boundary that has a DP on-site.

    Tuesday, December 17, 2013 8:48 PM
  • Just for test, can you flip it to download and try again?
    • Edited by skywalker123 Wednesday, December 18, 2013 2:53 PM
    Wednesday, December 18, 2013 2:53 PM
  • It didn't change the result unfortunately.
    Wednesday, December 18, 2013 5:41 PM
  • OK, do you have any conditions specified on your options tab in task sequence step to install applications?
    This could be also specified on a folder. Can you double check all of those?

    This is the last thing I can think of right now.

    Wednesday, December 18, 2013 8:57 PM
  • Nothing that shouldn't be there - and the step is attempting to execute so I know that the conditions are working as expected.
    Wednesday, December 18, 2013 8:59 PM