With the announcement Thursday that Microsoft will no longer use the “Semi-Annual Channel Targeted” mumbo-jumbo, we're left with dozens.
![Channel Channel](/uploads/1/2/5/6/125601968/212806173.jpg)
Starting with Windows 10, Microsoft provides quality and feature updates for Windows on an ongoing basis. The new release strategy-called Windows as a service-means IT admins need to adjust the way they have typically planned for OS deployments.
In this course, Microsoft MVP Joli Ballew walks admins through a summary of Windows as a service, and presents the major considerations for successful deployments. She explains the difference between the semi-annual and long-term servicing channels, the advantages of becoming a Windows Insider, and strategies for minimizing risk with deployment rings and build testing. She also covers servicing tools such as Windows Update, Windows Update for Business, Windows Server Update Services, and System Center Configuration Manager, which offer different degrees of control, including deferment and targeting options.
When changing an Office 365 client channel (using registry / SCCM / whatever you prefer), this does not change the installation version.When moving from the monthly to semi-annual channel, you're moving to a channel that is many revisions behind (that is part of the channel's purpose, I understand). However, since the client version is behind, how are updates for the semi annual channel applied? The client believes it is ahead of the semi-annual channel.Example:client was monthly, updated to 16.0.1client is now semi-annual, version is still 16.0.1In this scenario, the semi annual client will never update, until it reaches a revision higher than the installed monthly version. Is that correct?, because that is what I'm seeing for clients I cut over to semi-annual channel, using SCCM.This raises security concerns, since a semi-annual channel client will be out of date (insecure) for some time before it catches up to the monthly channel.I'm trying to avoid re-installing office 365 at every desktop, just to get the semi-annual channel clients back on track with updates. Are you sure? I'm checking SCCM's reporting for computers in a state of 'required', for Office 365 client updates, which all my computers should be, since the update has not yet been deployed. Office 365 client updates arrive in one package.The Office 365 client that is now on the semi-annual update channel does not qualify for the monthly channel update, Build 8.The Office 365 client also does not qualify for the semi annual channel update, Build 9126.2336.The client seems to be stuck between qualifying for any update, as mentioned earlier.
TJWilliamsWS wrote:Are you sure? I'm checking SCCM's reporting for computers in a state of 'required', for Office 365 client updates, which all my computers should be, since the update has not yet been deployed. Office 365 client updates arrive in one package.The Office 365 client that is now on the semi-annual update channel does not qualify for the monthly channel update, Build 8.The Office 365 client also does not qualify for the semi annual channel update, Build 9126.2336.The client seems to be stuck between qualifying for any update, as mentioned earlier.As you mentioned, the semi-annual channel build number is lower than the monthly channel build version.
However, you don't need to deploy an entirely new build in order to get security updates. We don't use SCCM, so I can't help you with it. However, we deploy Office security updates using WSUS while remaining on the semi-annual track.