System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Allow Applications with interactive deployment methods in a task sequence

In SCCM 2007 we utilized package with multiple programs. One install program that was silent to be used in a task sequence. One with interaction (appdeploy toolkit e.g.) for distribution to existing PCs. Once we moved to application we created multiple deployment methods with the appropiate filters. However if one of the deployment methods does contain the 'allow interact' option the application can not be added to a task sequence even though there are deployment methods that would apply to a OSD situation were it would pick the non-interactive one. Would like to see a logic check in the task sequence editor or the option to force a specific deployment method(s).

80 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Frank den Haan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
Noted  ·  sangeev responded  · 

Updated by bobmn for sangeev/OSD


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
An error occurred while saving the comment
  • Dave Lee commented  ·   ·  Flag as inappropriate

    Same problem here. I want to continue using Applications so think I'm going to have to create additional Application objects to be used solely by OSD task sequences +1 for logic in TS editor to force specific deployment method.

  • Johan Pol commented  ·   ·  Flag as inappropriate

    This is really required...or how do others solve this issue ?
    Create two applications ? Or still making packages ?

  • Oliver commented  ·   ·  Flag as inappropriate

    came accross this behaviour these days ... would like to see a solution soon :-)

  • Patrick Tilsen commented  ·   ·  Flag as inappropriate

    I'm surprised this doesn't have more votes. For anyone trying to deploy an application that in one deployment type requires user interaction, but in another does not, this missing feature seriously limits the usefulness of the Application model.

    It's also not well-explained or documented, so it's very easy for an inexperienced SCCM user to create an Application with one deployment type that prevents it from being used in a task sequence.

Feedback and Knowledge Base