Jan 21 2021 06:00 AM
Hi, I wanted to know the real definition/behavior for quality update deadlines.
Let's say we set it to 2days. For already WUFB managed, I understand it means the devices will reboot two days after the end of the deferal
But lets say I add an existing sccm managed device into co-management for WUFB, 10days after patch Tuesday, if there's no grace period set, will the device start to see the update right away, since it's past the 2 days deadline or will it still wait for the 2 days (meaning the deadline starts when the device sees that it has an update to install?
Thank you in advance and don't hesitate if you have any questions.
Jan 21 2021 09:11 AM
@lalanc01 for Quality Update deadline starts countdown from the time of calculated "offering" (aka when would have the update first been offered to the device based on Quality Update deferral policy and Quality Update pause). Grace period starts countdown from time of reboot pending.
Behavior: The Device will try to download and install at a convenient time based on the update stacks determination. Once pending reboot is reached the device tries to update outside of active hours by notifying the end user, once effective deadline is reached (calculated as the max of (QU offering date + deadline, reboot pending + grace period) it tries to update during active hours and a device is forced to reboot once the deadline has been reached. Note, if the device has not completed download/install when the deadlines has mostly elapsed they will happen as quickly as possible.
Does this help to answer your question? As you can see from the above Grace period is really almost never used outside of cases when the device was offline (such as a vacation) for a duration after the update was supposed to be offered.
Jul 14 2021 03:57 AM
Jul 14 2021 04:59 AM