Enable configuration of deadline randomization per-deployment
Currently, deadline randomization is a client setting that applies to all deployments targeted to systems; however, there are many cases where selectively enabling or disabling deadline randomization would be ideal. For example, many customers disable deadline randomization because it affects application deployments (which are often deployed to a subset of systems and impacts user communications/expectations/predictability about deployment timing), even though they see benefits of enabling it particularly for software updates (which are often deployed to most systems). Deadline randomization can significantly reduce the resource demand on the ConfigMgr infrastructure when deploying several software updates to many systems. Having deadline randomization configurable per-deployment would address this specific example and many other scenarios that could be cited that would justify the request for this important feature enhancement.
Regarding the subject of "software updates", you could try the new "phased deployement" feature in addition with the "Gradual deployement" option. This should do the trick !
The documentation on this only describes this setting as affecting software updates. Have you seen it apply to all software deployments?
> Disable deadline randomization
This setting determines whether the client uses an activation delay of up to two hours to install required software updates when the deadline is reached. By default, the activation delay is disabled.
Would be very helpful to randomize the deadline and the download start time (available start time) for specific deployments, but not in general. Like we already have it for the ConfigMgr Agent AutoUpdate (7 days) to really spread load. Likely a very good idea for Software Updates to spread load for scanning, download and installation over a defineable time.