Allow 2 sets of user experience options for deployment of application with supersedence
Consider this scenario: You have an application deployed as Available. You create a new application that supersedes the original application and deploy it as Available but with the option to automatically upgrade any superseded versions of the application.
I would like to customize the user notification options so I can select "Display in Software Center, and only show notifications for computer restarts" when it is available, but select "Display in Software Center and show all notifications" when it becomes required to upgrade a superseded version.
L U commented
I agree - understanding that the deployment has both "Required" and "Available" parts means both need to be configurable differently.
When superseding application is 'Available' these options are greyed out, but when we tick "Automatically upgrade any superseded versions of this application", then the User Experience activities to be performed outside the maintenance window, should be allowed: Software Installation and System Restart, And get back the option to prevent restart on a server.
By the way, the supersedence 'Uninstall' action runs as soon as the policy on the PC is updated, removing the old version, but the new version does not automatically install, it seems to be waiting (for that annoying maintenance window) even though it's not necessary to wait.
And some sites would not want the uninstall to go straight away, so the maintenanance window options should be made configurable, and apply to the removal of the previous version too, instead of what we have now: the removal running straight away, and the new install waiting till the evening.
BUG: I would classify the inconsistent behaviour above as a bug, which could be resolved by activating the configuration of the Maintenance Window options in the SCCM console, and tying both the old removal and the new install to those configured maintenance window options.