Software update deployment flexibility
Currently, there are two options that can be configured in CM to control when update actions occur on CM client devices. One allows us to set a date/time for when updates are available. The other sets a deadline date/time when updates are to be installed and a reboot process is initiated. My recommendation is to divide these two update scheduling options into three options.
- When updates are available (date/time)
- When updates must be installed by (date/time)
- When a reboot must occur by (following the installation of updates)
The option for when a reboot occurs should allow for multiple possibilities, such as "X" hours after updates are installed (within 1 hour, 2 hours, etc.) or a reboot must occur by a specific date/time.
An example scenario would be to make updates available on Friday (the client can download the updates once they are deployed in SCCM but they aren't "available" to install until the set date/time). Then maybe make the deadline to install updates Saturday at noon and a reboot deadline for Monday morning (say 06:00 AM). If someone turns their device off over the weekend, the updates would (could) install immediately when they turn it back on (if the deadline has passed). Give us (admins) an option to allow "X" hours following update installation before reboots occur.
We (our users) need more flexibility.