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.
![](https://patchmypc.aha.io/attachments/6707238157721126161/token/da490ac637fdd0c7c6487119cf1b1185bb7b0b5c4bdbf18e0b0d01bcf4353582.download?size=original)
We are adding this idea based on previous customer feedback via email, forum, and community.
Previously submitted on the forum:
https://patchmypc.com/forum/index.php?topic=2974
@Claudio, splitting this into a new idea here: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-241 please up-vote this idea
please move the applications and packages to some subfolder after creating them.
@Paul, could you not use multiple deployment types in this scenario with one checking if OSD is being run as a requirement?
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.
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.
Hey Mark, can you provide a scenario where you would rather create a package instead of an application?
Or maybe let us choose per app if it created a package or an application?