Change how software update maximum runtime is used in maintenance windows
Currently, when a software update group is deployed to a device with a maintenance window, the estimated time required is calculated from the maximum runtime of each update. If this time is longer than the available maintenance window, the updates are not installed. The maximum runtime of updates has been increasing and the total maximum runtime is often longer than reasonable maintenance windows.
I propose instead of calculating the total maximum runtime, each update be handled individually and compared to the remaining time in the maintenance window. For example, update 1 has a maximum runtime of 60 minutes. There is 90 minutes remaining in the MW, so installation proceeds and completes in 10 minutes. Update 2 also has a max runtime of 60 minutes. There are 80 mins remaining, so it proceeds. Using this method, both updates were able to install. Using the current method, the maintenance window would be skipped.