133 votesMartin Lindberg commented
1. Sometimes I want the clients to run installation files directly from a network share, without having to download content to local cache. Application model doesn't support that.
2. I often use "PS App Deployment Toolkit" in conjunction with SCCM, that gives me a lot of benefits and a better experience for end users. Let's say I'm deploying a big sized CAD-program. I then use PSADT to force the user to shut down necessary programs, but I also give them opportunity to defer and postpone the installation, for example 3 times. Thanks to deploying the script as a package, I can schedule to run the deployment recurring every day at 8 am, and "rerun if failed previous attempt". With Application model I can not make a custom recurring schedule. With Application model, if a user defers the installation once, it will ask again the next time Software Deployment evaluation cycle is run. I know I can customize that value in client settings, but I want to do it on a per application basis.
These are some examples why I often need Packages.Martin Lindberg commented
I still need package model and it’s not a nice user experience when half of the software in SC has proper icons, and half om them doesn’t. End users don’t care for packages or applications, for them it’s just software.
Updating status to started.
The first iteration/slice of this is available in the 1905 Tech Preview.
Phase 1 of these feature is in 1602 production