Plenty of times I have noticed that different organizations use Task Sequences(TS), Applications and packages only within the Application Management space of SCCM. Additionally, these are used with incorrect strategies where TS’s and Packages are used to push out Applications. With the release of 1706 and 1910, SCCM administrators now have the options for Scripts and Application Groups respectively.

  • To learn more about how to create and deploy SCCM Scripts, go here.
  • To learn more about how to Create and use SCCM Application Groups, go here.

To simplify the need on how to assess what strategy to use, I put the table below that answers the core questions on when to use each model within the Application Management models.

SCCM TASK SEQUENCE SCCM APPLICATION SCCM APPLICATION GROUPS SCCM PACKAGE SCCM SCRIPT
Device / User Intended for device only deployment Intended for device/user deployment Intended for device/user deployment Intended for device deployment but can be targeted to a User Intended for device only deployment
Approval for User No Yes Yes No No
Detection Methods May contain detection methods (an installation only runs if all conditions are met) Contains detection methods (an installation only runs if all conditions are met) Contains detection methods (an installation only runs if all conditions are met) No Detection method No Detection method
Parameters No No No No Yes
Superseded Older versions of an application can be superseded. The new version installs without having to deploy it. Older versions of an application can be superseded. The new version installs without having to deploy it.
State-Full / Stateless Better suited for state-full systems Better suited for state-full systems Better suited for state-full systems Better suited for state-less systems Better suited for state-less systems
Execution Location Needs to be downloaded to the local machine first before installation Needs to be downloaded to the local machine first before installation Needs to be downloaded to the local machine first before installation Can be executed from the SCCM Distribution Point directly
Store Supports Apple, Google and Windows Store Supports Apple, Google and Windows Store Supports Apple, Google and Windows Store
File Yes Yes Yes Yes / No No
Multi-Threading Partially Yes Partially Yes No Yes
Initiation Client or Server can initiate User or System can initiate User or System can initiate System can initiate System can initiate
User Impact High Low / Medium / High Low / Medium / High Low/ Medium Low/ Medium
Can you Pre-Stage? Yes Yes Yes Yes No
Repeat deployments Yes No No Yes No
Needs to be Online during deployment No No No No Yes
Complexity High Medium / High High Low / Medium Low
Maintenance Windows Yes Yes Yes Yes No