Patch My PC Feature and Application Request

A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:

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
    15 Jul, 2019 06:55pm

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

  • Claudio Mendes commented
    15 Jul, 2019 03:04pm

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

  • Admin
    Justin Chalfant commented
    2 Jul, 2019 08:39pm

    @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
    2 Jul, 2019 07:22pm

    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
    26 Jun, 2019 02:08pm

    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
    26 Jun, 2019 01:59pm

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

  • Mark Roberts commented
    26 Jun, 2019 12:25pm

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

  • +34