Forum Discussion
lalanc01
Jan 21, 2021Iron Contributor
WUFB Deadlines
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 afte...
Ricky_Kong
Jul 14, 2021Copper Contributor
Hi Aria,
I have similar question like lalanc01 and I was part of the WCCP WUfB Neighborhood in Teams that you organized. Do you have explanation for Deadline and Grace Period? I noticed that when I put the Deadline of 2 day and Grace Period of 0 days. After MS released a new patch and it installed on my machine will prompt with 2 days (instead of 0 days) until auto restart. Then what is the function of grace period in here?
I have similar question like lalanc01 and I was part of the WCCP WUfB Neighborhood in Teams that you organized. Do you have explanation for Deadline and Grace Period? I noticed that when I put the Deadline of 2 day and Grace Period of 0 days. After MS released a new patch and it installed on my machine will prompt with 2 days (instead of 0 days) until auto restart. Then what is the function of grace period in here?
lalanc01
Jul 14, 2021Iron Contributor
Grace period is used when someone is back from vacation so it gives an extra X days for the reboot to happen so the user isn't forced to reboot right away.
Here's what the doc says:
For feature updates, the deadline and grace period start their countdown from the time of a pending restart after the installation is complete. As soon as installation is complete and the device reaches pending restart, the device will try to update outside of active hours. Once the effective deadline is reached, the device will try to restart during active hours. (The effective deadline is whichever is the later of the restart pending date plus the specified deadline or the restart pending date plus the grace period.)
For quality updates, the deadline countdown starts from the time the update is offered (not downloaded or installed). The grace period countdown starts from the time of the pending restart. The device will try to download and install the update at a time based on your other download and installation policies (the default is to automatically download and install in in the background). When the pending restart time is reached, the device will notify the user and try to update outside of active hours. Once the effective deadline is reached, the device will try to restart during active hours.
Here's what the doc says:
For feature updates, the deadline and grace period start their countdown from the time of a pending restart after the installation is complete. As soon as installation is complete and the device reaches pending restart, the device will try to update outside of active hours. Once the effective deadline is reached, the device will try to restart during active hours. (The effective deadline is whichever is the later of the restart pending date plus the specified deadline or the restart pending date plus the grace period.)
For quality updates, the deadline countdown starts from the time the update is offered (not downloaded or installed). The grace period countdown starts from the time of the pending restart. The device will try to download and install the update at a time based on your other download and installation policies (the default is to automatically download and install in in the background). When the pending restart time is reached, the device will notify the user and try to update outside of active hours. Once the effective deadline is reached, the device will try to restart during active hours.