Windows Server – Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC)

Update March 2018: Microsoft Updated some of the information about the use cases of the Semi-Annual Channel and the LTSC for Windows Server. In short the Semi-Annual Channel releases are focusing on Container innovation and the infrastructure feature and roles are now features and roles of the LTSC.

I was already blogging about the new Windows Server servicing options including the Long-Term Servicing Channel (LTSC) and the new Semi-Annual Channel (SAC) options. It seems that there is a lot of confusion about what the purpose and the advantages of the Semi-Annual Channel releases. With that blog post I will try to explain what both servicing options are and when which servicing option should be used. Especially since SAC releases, like Windows Server 1709, will only be available as Windows Server Core. Spoiler alert: Windows Server Semi-Annual Channel releases are not for everyone and everything.

Windows Server Long-Term Servicing Channel (LTSC)

The Long-term Servicing Channel is the release model you’re already familiar with (currently called the “Long-term Servicing Branch”) where a new major version of Windows Server is released every 2-3 years. Users are entitled to 5 years of mainstream support, 5 years of extended support, and optionally 6 more years with Premium Assurance. This channel is appropriate for systems that require a longer servicing option and functional stability. Deployments of Windows Server 2016 and earlier versions of Windows Server will not be affected by the new Semi-annual Channel releases. The Long-term Servicing Channel will continue to receive security and non-security updates, but it will not receive the new features and functionality.

Example for Long-Term Servicing Channel releases

Windows Server 2008 R2

Windows Server 2012

Windows Server 2012 R2

Windows Server 2016

Long-Term Servicing Channel installation options

Windows Server Core

Windows Server with Desktop Experience

Windows Server Core as a container Image

Use cases for Long-Term Servicing Channel releases

As use cases for the Long-Term Servicing Channel releases you can basically count everything in which need predictable long term support, do not support Windows Server Core and where you don’t use the new features included in the Semi-Annual Servicing Channel releases and you prefer less updating.

General Purpose File Server – Traditional information worker file server which need long term support

– Traditional information worker file server which need long term support Legacy Software – Legacy software which do not support server core

– Legacy software which do not support server core Static Software – Software which does not leverage any of the new features of Semi-Annual Channel releases, which need predictable long term support

– Software which does not leverage any of the new features of Semi-Annual Channel releases, which need predictable long term support Legacy Hardware – End of life hardware

– End of life hardware SQL Server – Traditional databases with long lifecycles which need predictable long term support

– Traditional databases with long lifecycles which need predictable long term support Active Directory and other infrastructure roles – which benefit from long term support

– which benefit from long term support Hyper-V and Cluster nodes for Hyper-converged scenarios

nodes for Hyper-converged scenarios Hyper-V hosts which are benefiting from continuous innovation

Semi-Annual Channel (SAC)

The Semi-annual Channel releases will deliver new functionality for customers who are moving at a “cloud cadence,” such as those on rapid development cycles or service providers keeping up with the latest Hyper-V and Storage investments. Windows Server products in the Semi-annual Channel will have new releases available twice a year, in spring and fall. Each release in this channel will be supported for 18 months from the initial release.

Most of the features introduced in the Semi-annual Channel will be rolled up into the next Long-term Servicing Channel release of Windows Server. The editions, functionality, and supporting content might vary from release to release depending on customer feedback.

The Semi-annual Channel will be available to volume-licensed customers with Software Assurance, as well as via the Azure Marketplace or other cloud/hosting service providers and loyalty programs such as MSDN.

Example for Semi-annual Channel releases

Windows Server 2016 Nano Server

Windows Server 1709

Windows Server 1803

Semi-annual Channel installation options

Windows Server Core

Windows Server Core Container Image

Windows Server Nano Server Container Image

Use cases for Semi-annual Channel releases

Use cases for the Semi-annual Channel releases right now are application and services which leverage new feature very quickly and go with cloud cadence.

Lift and Shift applications into Containers

New cloud-based applications

Applications which can be quickly and easily redeployed

Linux containers on Windows Server

Hyper-V and Cluster nodes for Hyper-converged scenarios

Hyper-V hosts which are benefiting from continuous innovation

Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC) Overview

To make it a little easier, here is a quick overview of the two servicing channels:

Long-Term Servicing Channel Semi-Annual Channel Recommend Scenarios General purpose File Servers, SQL Servers, Active Directory and other infrastructure roles Containerized applications and container hosts, Hyper-converged hosts benefiting form faster innovation New Releases Every 2-3 years Every 6 months Support 5 years of Mainstream support +5 years of Extended support 18 months Editions All available Windows Server editions Standard and Datacenter Installation Options Server Core and Server with Desktop Experience Server Core only Licensing All customer through all channels Software Assurance and Cloud customers only

Conclusion

As you can see, Windows Server Semi-annual channel are not designed for everyone. And if you don’t feel comfortable with Windows Server Core (btw you should check out Microsoft Project Honolulu), the fast release cadence or the short support life cycle you should go with the Windows Server Long-Term Servicing Channel. You will not lose anything you had today, you still will get new versions every 2-3 years with all the options you had today. If you need the fast innovation and you get something out of the new features the Semi-annual channel will provide you with 2 releases a year. But make sure, that your deployment, configuration and management is automated, otherwise you will suffer from the fast release cadence. I have three other very important points I want to make sure you know about:

Not all your servers have to go with LTSC only or SAC only – as long as you have the right licensing in place you can choose for each server, which ever fits your needs best.

– as long as you have the right licensing in place you can choose for each server, which ever fits your needs best. You don’t have to switch now – you can also decided to go with LTSC today and switch to a SAC release as soon as you benefit from it. You can also switch back to LTSC from SAC if you don’t like it. (With Switch I mean redeploy)

– you can also decided to go with LTSC today and switch to a SAC release as soon as you benefit from it. You can also switch back to LTSC from SAC if you don’t like it. (With Switch I mean redeploy) Upgrades are not in-place – It doesn’t matter which servicing channel you are using, servers need to be redeployed. (Not like in Windows 10 where you can leverage in-place upgrades)

I hope this helps to understand the point about Windows Server Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC). The Semi-Annual Channel releases are a new offer from Microsoft for customers to get their hands on new features much quicker, this offers a huge benefit if you can make use of it. But Microsoft is not forcing you to use SAC, LTSC for some scenarios and customers is still the better option. So both solutions are having huge value in different scenarios.