WUFB Deadlines

%3CLINGO-SUB%20id%3D%22lingo-sub-2082405%22%20slang%3D%22en-US%22%3EWUFB%20Deadlines%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2082405%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20wanted%20to%20know%20the%20real%20definition%2Fbehavior%20for%20quality%20update%20deadlines.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet's%20say%20we%20set%20it%20to%202days.%20For%20already%20WUFB%20managed%2C%20I%20understand%20it%20means%20the%20devices%20will%20reboot%20two%20days%20after%20the%20end%20of%20the%20deferal%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20lets%20say%20I%20add%20an%20existing%20sccm%20managed%20device%20into%20co-management%20for%20WUFB%2C%2010days%20after%20patch%20Tuesday%2C%20if%20there's%20no%20grace%20period%20set%2C%20will%20the%20device%20start%20to%20see%20the%20update%20right%20away%2C%20since%20it's%20past%20the%202%20days%20deadline%20or%20will%20it%20still%20wait%20for%20the%202%20days%26nbsp%3B%20(meaning%20the%20deadline%20starts%20when%20the%20device%20sees%20that%20it%20has%20an%20update%20to%20install%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20in%20advance%20and%20don't%20hesitate%20if%20you%20have%20any%20questions.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2082405%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ewufb%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2083234%22%20slang%3D%22en-US%22%3ERe%3A%20WUFB%20Deadlines%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2083234%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F332021%22%20target%3D%22_blank%22%3E%40lalanc01%3C%2FA%3E%26nbsp%3Bfor%20Quality%20Update%20deadline%20starts%20countdown%20from%20the%20time%20of%20calculated%20%22offering%22%20(aka%20when%20would%20have%20the%20update%20first%20been%20offered%20to%20the%20device%20based%20on%20Quality%20Update%20deferral%20policy%20and%20Quality%20Update%20pause).%20Grace%20period%20starts%20countdown%20from%20time%20of%20reboot%20pending.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBehavior%3A%20The%20Device%20will%20try%20to%20download%20and%20install%20at%20a%20convenient%20time%20based%20on%20the%20update%20stacks%20determination.%20Once%20pending%20reboot%20is%20reached%20the%20device%20tries%20to%20update%20outside%20of%20active%20hours%20by%20notifying%20the%20end%20user%2C%20once%20effective%20deadline%20is%20reached%20(calculated%20as%20the%20max%20of%20(QU%20offering%20date%20%2B%20deadline%2C%20reboot%20pending%20%2B%20grace%20period)%20it%20tries%20to%20update%20during%20active%20hours%20and%20a%20device%20is%20forced%20to%20reboot%20once%20the%20deadline%20has%20been%20reached.%20Note%2C%20if%20the%20device%20has%20not%20completed%20download%2Finstall%20when%20the%20deadlines%20has%20mostly%20elapsed%20they%20will%20happen%20as%20quickly%20as%20possible.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDoes%20this%20help%20to%20answer%20your%20question%3F%20As%20you%20can%20see%20from%20the%20above%20Grace%20period%20is%20really%20almost%20never%20used%20outside%20of%20cases%20when%20the%20device%20was%20offline%20(such%20as%20a%20vacation)%20for%20a%20duration%20after%20the%20update%20was%20supposed%20to%20be%20offered.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

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. 

3 Replies

@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.

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?
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.