Windows 10: Windows Semi-Annual Channel and Targeted Deployment

Brink · Jul 28, 2017

As you may have already seen on the Windows Experience blog, yesterday we announced that the Windows 10 Creators Update is ready for broad deployment. Additionally, we announced a transition from the Current Branch (CB) and Current Branch for Business (CBB) model of Windows releases to a more predictable, twice-yearly release cadence called the Semi-Annual Channel. With the Semi-Annual Channel, each year we are targeting the release of two Windows Feature Updates, one in March and the other in September, each of which with an 18-month servicing timeline. You can read more about this new Semi-Annual Channel at the Windows for IT Pros blog in Windows as a service: Simplified and Aligned.

Along with this change comes some new terminology, specifically the terms targeted and broad deployment. While these terms roughly correspond with the CB and CBB nomenclature that we've used in the past, they are not an exact translation of these terms and are defined a little differently:

Targeted deployment refers to the phase immediately following the release of a new Windows version when it is recommended to conduct your organization's piloting process and to begin deployments to select devices, such as those with the most modern chipsets and capabilities. Surface devices make excellent candidates for these targeted deployments.

Broad deployment refers to the phase that follows targeted deployment, where your organizations' pilots and targeted deployments have provided successful feedback and Windows has been vetted for deployment to most or all of your organization's devices.

You can read about these new terms and recommended deployment practices in the updated Update Windows 10 in the enterprisesection of Windows Docs, or, for a five-minute video overview, see the Updates to the Windows as a Service model Microsoft Mechanics video.

Where does Surface fit into this process?

Surface devices make excellent candidates for piloting and targeted deployments. The modern form factor, chipsets, and Microsoft-tested and approved environment make Surface devices the logical choice for your first wave of deployments in the targeted phase. You'll also find the latest features and capabilities of Windows on Surface first, like the integration of power management with the Power Slider on Creators Update found first on Surface Pro and Surface Laptop and now available on Surface Pro 4.

New devices also make excellent candidates during the targeted deployment timeframe, especially if your organization's purchase of new hardware aligns with the targeted phase. Not only will these new devices feature the latest chipsets, features, and capabilities, but deploying the latest Windows version to your newest devices helps to eliminate duplication of effort. It makes far more sense to deploy once, with the latest build of Windows, than to deploy your new devices with your organization's standard image for broad deployment, resulting in the need to redeploy those devices again when your organization makes the move to a newer version of Windows.

Visit the Surface IT Center to learn more about Surface devices and the IT practices and tools that make Surface the right choice for business.
Click to expand...

Source: The Windows Semi-Annual Channel and Targeted Deployment Surface

cereberus · Jul 29, 2017

This is a nice paragraph from link below which sums it up very clearly.

Windows as a service: Simplified and Aligned Windows for IT Pros

As part of the alignment with Windows 10 and Office 365 ProPlus, we are also adopting common terminology to make it as easy as possible to understand the servicing process. The two most important terms to understand:

Semi-Annual Channel. These are the twice-per-year feature update releases, targeting March and September, designed for the broad population of general-purpose PCs used throughout organizations. Each of these releases will be serviced for 18 months from the date of release. (The Semi-Annual Channel replaces the Current Branch [CB] and Current Branch for Business [CBB] concepts.)
Long-Term Servicing Channel. These are less frequent releases, expected every 2-3 years (with the next one expected in 2019), designed for special-purpose PCs such as those used in point-of-sale systems or controlling factory or medical equipment. Each of these releases will be serviced for 10 years from the date of release. (The Long-Term Servicing Channel replaces the Long-Term Servicing Branch [LTSB].)

:)

Frazer-IT · Jul 29, 2017

Windows 10 ver. 1709 downloads even with Current Branch for Business selected in ver. 1703

On all of the 100-plus PCs in our office, we are running Windows 10 Pro version 1703, with Current Branch for Business selected. Last week, after the November Patch Tuesday updates were released, some of our PCs started to download version 1709. We don't
want version 1709 until we can test it to make sure it doesn't break something in our workflow.

Selecting Current Branch for Business is supposed to defer the feature update for approximately 4 months from the release of the update. That was the way it worked with the roll-out of version 1703, and that worked well for us. However, that procedure
seems no longer to be working.

It is my understanding that Current Branch for Business is deprecated in favor of Semi-Annual Channel (without the "Targeted" indicator). I spent a lot of time yesterday trying to find out how to set a PC running Windows 10 version 1703 to Semi-Annual
Channel, without success.

How does one do that?

DavidMcCartney1 · Jul 29, 2017

Remote Desktop Shadow not working in Creators Update

I agree, Server 2012R2 is Windows 8 Server and the KB mentioned does not apply to Windows 10 / Server 2016.

Server 2016 appears to allow you to choose your release channel (Starting with 1709). Semi-Annual channel (Like Windows 10) or Long-Term channel (5 Year). The latest Long-Term channel release is 1607, so it is unlikely they are experiencing this issue.

Is anyone experiencing remote shadowing issues on Server 2016 release 1709?

Windows 10: Windows Semi-Annual Channel and Targeted Deployment

Windows Semi-Annual Channel and Targeted Deployment

Windows Semi-Annual Channel and Targeted Deployment

Windows Semi-Annual Channel and Targeted Deployment

Windows Semi-Annual Channel and Targeted Deployment - Similar Threads - Semi Annual Channel

Stuck on Semi-Annual Enterprise Channel

Office 365 Semi-Annual Targeted v2002 build 12527.20442 - April 14

Office 365 Semi-Annual Targeted v2002 build 12527.20278 - March 10

Choose when updates are installed (Semi annual channel / Targeted) option disappeared in 1909

Office 365 Semi-Annual (Targeted) v1902 build 11328.20286 - May 14

Difference between Semi-Annual Channel and Semi-Annual Channel (targeted) in regards to...

Windows 10 and the disappearing Semi-Annual Channel Targeted (SAC-T)

Windows Server version 1803 Semi-Annual Channel update

Office 2016 & Office 365 Semi-Annual Targeted v1708 build 8431.2215