Enhance Phased Deployment for Applications
TL;DR: Make Phased Deployments for Applications the same as Phased Deployments for Task Sequences where you can create up to 10 phases and manually initiate the second phase of deployment.
Currently in 1806 although you can create a phased deployment for an Application, you're limited in two key areas:
1) You cannot manually create phases for an application
2) You cannot manually begin the second phase of deployment for an application
3) You are limited to 2 phases for an application
In our environment we follow a controlled graceful deployment process where an Application Model application is deployed office-by-office to prevent flood of support calls should an unexpected situation arise. Since we have multiple offices across the globe, a single application may have as many as 13 deployments, although it's typically around 6.
Phased Deployments is the solution here but it's usefulness in the context of Applications is limited. If it could match features available in Task Sequence deployments it would be of significant value.
Noted and thanks for the feedback!
On 1902 here as well and I think the Phased Deployment concept is great and saves me a lot of hassle, but in addition to the OP's ideas, I would very much like the ability to control the user experience fully so that I can hide deployments in Software Center. Currently I have an app I want to deploy to my whole estate but I really don't want the users to see it/be bugged about it. As things stand, I simply can't use Phased Deployments for this, which is a real shame!
Would really love this as well.
We are in a similar situation with our deployments and currently create upwards of 8 deployments on applications where we do phased rollouts.
This is time consuming and tedious, and a phased application deployment would solve this nicely.
Currently on 1902 OPs remarks still stand.
I would like to add that there is no way to control "User Experience" settings in a phased deployment. These settings are necessary to control the impact on end users. Some things are not needed to be seen. Some need to occur outside maintenance windows.
Kris Titeca commented
I would also suggest to allow the ability to provide a timeframe for the deadline, especially when you opt for making available the software gradually. Having laptops with a deadline in the middle of the night is not the best experience. Of course you can deal with that in other ways but still might be handy.