|

Semi-Annual Channel(SAC) Targeted release will be retired

ByJorge Pereira
Tags: , , ,

Yep – you heard correctly!

No more Semi-Annual Channel Targeted (aka CB) or  Semi-Annual Channel Broad (aka CBB) releases!

Although this is not a new topic (John Wilcox gave us a heads up back in May 2018)    the Semi-Annual Channel(SAC) Targeted release (formerly known as CB or Current Branch) will be fully retired after Windows 10 v1903.

What this means for Enterprises?

It will no longer be presented as an option in Window Update for Business. Instead, you will find a single entry for each new SAC release.

More importantly,   if you use System Center Configuration Manager, Windows Server Update Services (WSUS), or other management tools, there will now only be one feature update published to WSUS, and this will occur at the time of release.

Action Item:

For future upgrades beyond Windows 10, version 1903, you will need to establish an additional delay and recreate your deployments rings on the schedule you want, you will need to update your deferral value from 30 to 60 or  90 days.

For more information on this topic please see John Wilcox Febrary 14 blog post: Windows Update for Business and the retirement of SAC-T

Accomplished Information Technology services professional with over 25 years of experience performing technical pre-sales, solution selling, public speaking / presentations, consulting, project delivery and program management. Over the past few years, Jorge has focused on customers solutions in the areas of: Artificial Intelligence, Generative AI, Workforce transformation, End-User-Computing (EUC) Lifecycle Management, Modern Device Management, and Cybersecurity.

Disclaimer:  I work for Dell Technology Services as a Workforce Transformation Solutions Principal.    It is my passion to help guide organizations through the current technology transition specifically as it relates to Workforce Transformation.  Visit Dell Technologies site for more information.  Opinions are my own and not the views of my employer.

Similar Posts

Gathering Existing Devices Windows Autopilot Device IDs
|

Gathering Existing Devices Windows Autopilot Device IDs

ByJorge Pereira

Update 8/1/2020: Microsoft has updated their official blog post a number of times since this post to include automated ways from Intune and ConfigManager. We have published a number of posts about what Windows Autopilot is and how to setup and test. Now that so many organizations have taken note of Modern Device Management advantages…

Good Tweet From Test

Good Tweet From Test

ByJorge Pereira

This tweet from PaulCouvert is a great example of how AI can simplify workflows I've just created an ecommerce business using Dall-E 3. Almost everything is generated by AI and the website is created with a simple no-code tool. It took me less than 15 minutes and I'll show you how: pic.twitter.com/GlCzQMBVlw — Paul Couvert…

Microsoft 365 Versions Comparison
|

Microsoft 365 Versions Comparison

ByJorge Pereira

I wanted to write something  about a question I get often asked: What is the pricing and the differences between the different versions of Microsoft 365.   Microsoft has a variety of productivity and security management offerings that small to medium-sized and large enterprise customers may consider when upgrading their desktop and device infrastructure, each bringing…

Windows Autopilot Collecting Hash and More
|

Windows Autopilot Collecting Hash and More

ByJorge Pereira

PowerShell script that uses WMI to retrieve properties needed by the Microsoft Store for Business to support Windows AutoPilot deployment. https://www.powershellgallery.com/packages/Get-WindowsAutoPilotInfo/  Thank you  Michael Niehaus! For more  information see: Technet Blog Post Gathering Windows Autopilot hardware details from existing Devices Overview of Windows Autopilot | Microsoft Docs Deploy Windows 10 Enterprise for new devices with…