Patch My PC Feature and Application Request

A community where customers, consultants, MVPs, and the community can provide feedback to make a better product for everyone!

71 Vote

Base Installation Feature Should Create Applications not Packages in SCCM

The base installation feature available today in the publishing service uses the legacy package model in SCCM. It would be a better experience for it to create applications for base installations.

We are adding this idea based on previous customer feedback via email, forum, and community.

Previously submitted on the forum:

  • Justin Chalfant
  • Jun 26 2019
  • Attach files
  • Admin
    Justin Chalfant commented
    July 15, 2019 18:55

    @Claudio, splitting this into a new idea here: please up-vote this idea

  • Claudio Mendes commented
    July 15, 2019 15:04

    please move the applications and packages to some subfolder after creating them. 

  • Admin
    Justin Chalfant commented
    July 02, 2019 20:39

    @Paul, could you not use multiple deployment types in this scenario with one checking if OSD is being run as a requirement?

  • Paul Andrews commented
    July 02, 2019 19:22

    I have a specific use case, our package uses PADT and we have a check in place that looks to see if their is a pending reboot. If so, it prompts the user to reboot and then will install. For OSD we don't want any prompts so we run a different command in the same application but then publish it as a package.

  • Mark Roberts commented
    June 26, 2019 14:08

    I don't have a specific use case. Just thought to keep options open, but I agree that applications would be a better choice if picking one over the other.

  • Admin
    Justin Chalfant commented
    June 26, 2019 13:59

    Hey Mark, can you provide a scenario where you would rather create a package instead of an application?

  • Mark Roberts commented
    June 26, 2019 12:25

    Or maybe let us choose per app if it created a package or an application?

  • and 34 more