Microsoft Retires Windows 10 Semi-Annual Channel Targeted Releases
Windows Update for Business (WUfB) is a feature in Windows 10 that allows organizations to control how clients are updated without requiring any local infrastructure. In Windows 7 it was common to deploy Windows Server Update Services (WSUS) to control which updates were applied and when. Windows 10 can still be used with WSUS but WUfB provides a way to distribute updates without the costs involved in deploying WSUS.
For more information on how WUfB works and configuring it, check out Understanding Windows Update for Business and Windows 10 Tip: Configure Windows Update for Business using Group Policy on Petri.
As it stands in Windows 10 version 1809 and previous releases, you can choose to configure devices to update on the Semi-Annual Channel (SAC) or Semi-Annual Channel (Targeted). Devices set to update on SAC-T receive Windows 10 feature updates as soon as they are made available. But SAC deploys feature updates roughly three months after they are made generally available, or in other words, when Microsoft deems the update to be ‘business ready’. But it is up to you to make sure cumulative updates (CUs) get applied because the SAC release of Windows 10 is the same OS build as the previous SAC-T release. For example, the SAC-T release of Windows 10 version 1803 was OS build 17134.648 and the SAC release was the same OS build number.
A SAC Only World
As you are probably already aware, there are only two feature updates to Windows 10 each year. So, to simplify the terminology and release schedule, starting in Windows 10 19H1, Microsoft is retiring SAC-T. There will be no SAC-T ‘release’ of Windows 10 and the WUfB user interface will be updated to reflect this. There will be one SAC release for each Windows 10 feature update.
That means that if you currently have WUfB configured for SAC-T, when the upgrade to 19H1 happens, nothing will change. If you had a deferral period configured for SAC-T, it will be applied to SAC. If you have configured devices for SAC, any deferral period configured will have 60 days added to it for the upgrade to 19H1 only. Although you won’t see that change in the WUfB user interface as it will be handled on the service side by Microsoft. But after the upgrade to 19H1, the deferral value will be set to whatever it was before the upgrade.
Microsoft keeps changing how it delivers Windows 10 as a service and the support lifecycle for each version. Going forwards, if you want to delay the deployment of Windows 10 feature updates, you will need to set an appropriate deferral value for SAC. I appreciate there is an attempt to simplify the terminology here – especially as ‘Targeted’ implied that it updated a small group of devices – but it’s not clear if Microsoft will allow you to defer SAC deployment beyond 365 days in version Windows 10 19H1. For more information about these changes, see Microsoft’s website here.
More in Windows 10
IT Admins Report Issues With Microsoft Store Version of Quick Assist App
May 16, 2022 | Rabia Noureen
Microsoft Releases May 2022 Patch Tuesday Updates
May 11, 2022 | Laurent Giret
What’s New with Windows – April 2022
May 2, 2022 | Russell Smith
This Week in IT - Is Microsoft Killing Off Patch Tuesday?
Apr 22, 2022 | Russell Smith
Windows 10 November 2021 Update is Now Ready for Broad Deployment
Apr 18, 2022 | Rabia Noureen
This Week in IT - Windows 10 Gets Search Highlights and Is Microsoft in Hot Water Over Windows Cloud Pricing?
Apr 15, 2022 | Russell Smith
Most popular on petri