Allow to skip maintenance window for superseded appliciations made available to user collections
Currently when a superseding application is deployed to a user collection I can enable the option "Automatically upgrade any superseded versions of this application". With this option set I'm able to specify a scheduling for the deployment. But the option to allow the installation or maybe the system restart outside the maintenance windows is greyed out.
Would be nice to have the option to skip the maintenance windows for this type of deployment as well.
L U commented
I vote for this (I've run out of votes).
We need for deployments with supersedence to recognise there are both "Available" and "Required" components to the deployment and allow complete, separate configuration of the user experience options for both.
Aaron Young commented
Would definitely be great to to be able to specify to ignore maintenance windows when using the "Automatically upgrade superseded".
We deploy most of our applications as available. When we supersede, we want the option to force upgrade any device that has an older version.
When we do that right now, it's waiting for user interaction and then waits for a maintenance window.
We need an option to simply force the upgrade on any workstation that has this application installed.
Right now we need to create separate device collections to force the install of the new version.
+1. It doesn't help that we can't create maintenance windows specifically for application deployment only (like we can for software deployments and task sequences).
Agreed. So far in my testing, I have not been able to get the Available User Deployment with this setting working without user interaction. Would be nice for it to detect the superseded software and automatically upgrade it if checked.