Windows update workflow help!

[Rondelltron]

Good day and thank you in advance with any help / recommendations 

 

 

So i am learning a new environment and am tasked with highlighting if there is anything wrong with the way they update pc's.

What they do is in production they push out a legacy windows update profile.

every super tuesday they go to the device update module in WS1 and assign the KB to the Ring 1 , 2 and then production . 

 

Now im being told They should of stopped doing this a while ago as microsoft has depreciated this feature . So i ask if they want to continue pushing out the KB should they stop doing the approval and switch to using windows update profile only and just assigning profiles still doing ring based deployment 

 

 

 

 

 

 

 

 

 

 

 

 

[Glyn Dobson]

The Windows Update for Business process has evolved considerably over the past couple of years. The supported approach is now a ring-based deployment using deferrals instead of approvals. You will want to setup a few profiles with differing deferral values starting at no deferral for your UAT/Pilot with the next ring being 0+n days based on how long it will take you to validate the update. You would then progress through the next rings until your device fleet is updated. If there are any issues, you can use the pause and rollback functionality. Note that Quality updates (your "Patch Tuesday" updated) can be deferred for a maximum of 30 days with Feature updates being deferred for up to 365 days (although you would use the Target Release Version setting for this rather than deferral). If you need to pause an update, you can only do this for up to 35 days.

Here is a good TechZone article on Windows Updates with the most current and up to date details. https://techzone.omnissa.com/managing-updates-windows-devices-workspace-one-operational-tutorial

This is a link to the Microsoft technical documentation on the settings that are used to control Windows Update: https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update