Microsoft Windows Server 2016 was released in September 2016. So, when does it become end-of-life? There is a lot of false information about the EOL status of Windows Server 2016. We review the EOL status and what it means for the Windows Server 2016 administrator.
Windows Server 2016 follows the Fixed Lifecycle Licensing Policy. So, support for Microsoft Windows Server 2016 is slit into 2 halves. Each Fixed Lifecyle product of Microsoft comes with 2 different support:
- Mainstream support
- Extended support
Mainstream support is valid for 5 years from the release data. And, Extended support is valid for the successive 5 years once the mainstream support ends.
With a release data of September 2016, we now understand that the mainstream support for Windows Server 2016 is valid for the first 5 years. And, the successive 5 years of support will be called the Extended Support.
There is a difference in the scope of Mainstream support and Extended Support. So, we need to understand those differences to appreciate the Fixed Lifecycle Plan.
It may be pertinent to understand that Extended Support of a Fixed Lifecycle product is different that the ESU or Extended Security Updates programs.
So, for Windows Server 2016, the mainstream support ended on 11 January, 2022. The Extended Support for Windows Server 2016 will end on 12 January, 2027.
The question of the ESU program for Windows Server 2016 will be relevant after January 2027. So, there is no need to commit into buying any ESU for Windows Server 2016 until January 2027.
What does the Mainstream support mean?
The mainstream support for Windows Server 2016 ended in January 2022.
Mainstream Support is the first phase of the product lifecycle. At the supported service pack level, Mainstream Support for Windows Server 2016 includes:
- Incident support (no-charge incident support, paid incident support, support charged on an hourly basis, support for warranty claims)
- Security update support
- The ability to request non-security updates
For Windows Server 2016, the mainstream support ended in January 2022. So, we can conclude that product support for Windows Server 2016 in terms of feature updates and non-security updates will no longer be offered.
Thankfully, access to security updates for Windows Server 2016 is covered under the ‘Extended Support’.
What does Extended Support for Windows Server 2016 mean?
Extended Support for Windows Server 2016 begins after the mainstream support for the server ended in January 2022. Until 12 January 2027, Windows Server 2016 is eligible for Extended Support.
The Extended Support for Windows Server 2016 include the following:
- Security Updates to patch security vulnerabilities reported in Microsoft security bulletins.
Product support for Windows Server 2016 is not included in the Extended Support.
You can always buy a Service Pack for Windows Server 2016 to enjoy support for the product. But, for any product issues requiring Microsoft support, you will need to pay to get that support separately.
Extended Support for Windows Server 2016 started in January 2022 and will end in January 2027.
Security coverage for Windows Server 2016
So, the coverage for providing security updates for Windows Server 2016 includes a 10 year period that is comprised of 5 years of Mainstream support and 5 years of Extended support.
The ‘Patch Tuesday’ program for Windows Server 2016 will offer security updates for the server until January 2027. Post January 2027, you will need to enroll in the paid subscription program of the ESU program for Windows Server 2016.
Rajesh Dhawan is a technology professional who loves to write about Cyber-security events and stories, Cloud computing and Microsoft technologies. He loves to break complex problems into manageable chunks of meaningful information.
Windows Server Lifecycle (EOL)
Below you can find the life cycle for each version of operating system Windows Server, like Windows Server 2019 Datacenter, including release dates and end of life (EOL) dates.
References
- Microsoft
Microsoft
Founded in 1975, Microsoft (Nasdaq “MSFT”) is the worldwide leader in software, services, devices and solutions that help people and businesses realize their full potential.
Company website: http://www.microsoft.com
From Wikipedia, the free encyclopedia
Windows Server 2016
| Version of the Windows NT operating system | |
|
Screenshot of Windows Server 2016 with Desktop Experience |
|
| Developer | Microsoft |
|---|---|
| Written in |
|
| OS family | Windows Server |
| Working state | Current |
| Source model |
|
| Released to manufacturing |
September 26, 2016; 8 years ago[1] |
| General availability |
October 12, 2016; 8 years ago[2] |
| Latest release | 1607 (10.0.14393.7973) (April 11, 2025; 11 days ago[3]) [±] |
| Marketing target | Business |
| Update method | Windows Update, Windows Server Update Services, SCCM |
| Platforms | x86-64 |
| Kernel type | Hybrid (Windows NT kernel) |
| Default user interface |
Windows shell (Graphical) Windows PowerShell (Command line) |
| License | Trialware, Volume licensing, Microsoft Software Assurance, MSDN subscription, Microsoft Imagine |
| Preceded by | Windows Server 2012 R2 (2013) |
| Succeeded by | Windows Server 2019 (2018) |
| Official website | Windows Server 2016 (archived at Wayback Machine) |
| Support status | |
|
Windows Server 2016 is the eleventh major version of the Windows NT operating system produced by Microsoft to be released under the Windows Server brand name. It was developed alongside Windows 10 and is the successor to the Windows 8.1-based Windows Server 2012 R2. The first early preview version (Technical Preview) became available on October 1, 2014 together with the first technical preview of System Center.[5] Windows Server 2016 was released on September 26, 2016 at Microsoft’s Ignite conference[1] and reached general availability on October 12, 2016.[2]
It was succeeded by Windows Server 2019 and the Windows Server Semi-Annual Channel, which was released in 2017. Mainstream support for Windows Server 2016 ended on January 11, 2022, and extended support will end on January 12, 2027.
Windows Server 2016 has a variety of new features, including
- Active Directory Federation Services: It is possible to configure AD FS to authenticate users stored in non-AD directories, such as X.500 compliant Lightweight Directory Access Protocol (LDAP) directories and SQL databases.[6]
- Windows Defender: Windows Server Antimalware is installed and enabled by default without the GUI, which is an installable Windows feature.[7]
- Remote Desktop Services: Support for OpenGL 4.4 and OpenCL 1.1, performance and stability improvements; MultiPoint Services role (see Windows MultiPoint Server)[8]
- Storage Services: Central Storage QoS Policies; Storage Replicas (storage-agnostic, block-level, volume-based, synchronous and asynchronous replication using SMB3 between servers for disaster recovery).[9] Storage Replica replicates blocks instead of files; files can be in use. It’s not multi-master, not one-to-many and not transitive. It periodically replicates snapshots, and the replication direction can be changed.
- Failover Clustering: Cluster operating system rolling upgrade, Storage Replicas[10]
- Web Application Proxy: Preauthentication for HTTP Basic application publishing, wildcard domain publishing of applications, HTTP to HTTPS redirection, Propagation of client IP address to backend applications[11]
- IIS 10: Support for HTTP/2
- Windows PowerShell 5.1[12]
- Windows Server Containers [13]
Networking features
[edit]
- DHCP: As Network Access Protection was deprecated in Windows Server 2012 R2, in Windows Server 2016 the DHCP role no longer supports NAP[14]
- DNS:
- DNS client: Service binding – enhanced support for computers with more than one network interface[15]
- DNS Server: DNS policies, new DDS record types (TLSA, SPF, and unknown records), new PowerShell cmdlets and parameters[16]
- Windows Server Gateway now supports Generic Routing Encapsulation (GRE) tunnels[17]
- IP address management (IPAM): Support for /31, /32, and /128 subnets; discovery of file-based, domain-joined DNS servers; new DNS functions; better integration of DNS, DHCP, and IP Address (DDI) Management[18]
- Network Controller: A new server role to configure, manage, monitor, and troubleshoot virtual and physical network devices and services in the datacentre[19]
- Hyper-V Network virtualization: Programmable Hyper-V switch (a new building block of Microsoft’s software-defined networking solution); VXLAN encapsulation support; Microsoft Software Load Balancer interoperability; better IEEE Ethernet standard compliance.[20]
- Rolling Hyper-V cluster update: Unlike upgrading clusters from Windows 2008 R2 to 2012 level, Windows Server 2016 cluster nodes can be added to a Hyper-V Cluster with nodes running Windows Server 2012 R2. The cluster continues to function at a Windows Server 2012 R2 feature level until all of the nodes in the cluster have been upgraded and the cluster functional level has been upgraded.[21]
- Storage quality of service (QoS) to centrally monitor end-to-end storage performance and create policies using Hyper-V and Scale-Out File Servers
- New, more efficient binary virtual machine configuration format (.VMCX extension for virtual machine configuration data and the .VMRS extension for runtime state data)
- Production checkpoints
- Hyper-V Manager: Alternate credentials support, down-level management, WS-Management protocol
- Integration services for Windows guests distributed through Windows Update
- Hot add and remove for network adapters (for generation 2 virtual machines) and memory (for generation 1 and generation 2 virtual machines)
- Linux secure boot
- Connected Standby compatibility
- Storage Resiliency feature of Hyper-V is formed for detecting transitory loss of connectivity to VM storage. VMs will be paused until connectivity is re-established.[22]
- RDMA compatible Virtual Switch[23]
Microsoft announced a new installation option, Nano Server, which offers a minimal-footprint headless version of Windows Server. It excludes the graphical user interface, WoW64 (support for 32-bit software) and Windows Installer. It does not support console login, either locally or via Remote Desktop Connection. All management is performed remotely via Windows Management Instrumentation (WMI), Windows PowerShell and Remote Server Management Tools (a collection of web-based GUI and command line tools).[24] However, in Technical Preview 5, Microsoft has re-added the ability to administer Nano Server locally through PowerShell.
According to Microsoft engineer Jeffrey Snover, Nano Server has 93% lower VHD size, 92% fewer critical security advisories, and 80% fewer reboots than Windows Server.[25][26]
Nano Server is only available to Microsoft Software Assurance customers[2] and on cloud computing platforms such as Microsoft Azure and Amazon Web Services.
Starting with the new feature release of Windows Server version 1709, Nano Server can only be installed inside a container host.[27]
Microsoft has been reorganized by Satya Nadella, putting the Server and System Center teams together. Previously, the Server team was more closely aligned with the Windows client team. The Azure team is also working closely with the Server team.[28]
In March 2017, Microsoft demonstrated an internal version of Server 2016 running on the ARMv8-A architecture. It was reported that Microsoft was working with Qualcomm Centriq and Cavium ThunderX2 chips. According to James Vincent of The Verge, this decision endangers Intel’s dominance of the server CPU market.[29][30][31] However, later inquiry from Microsoft revealed that this version of Windows Server is only for internal use and only impacts subscribers of Microsoft Azure service.[32]
A public beta version of Windows Server 2016 (then still called vNext) branded as «Windows Server Technical Preview» was released on October 1, 2014; the technical preview builds are aimed toward enterprise users. The first Technical Preview was first set to expire on April 15, 2015 but[33] Microsoft later released a tool to extend the expiry date, to last until the second tech preview of the OS in May 2015.[34] The second beta version, «Technical Preview 2», was released on May 4, 2015. Third preview version, «Technical Preview 3» was released on August 19, 2015. «Technical Preview 4» was released on November 19, 2015. «Technical Preview 5» was released on April 27, 2016.
Windows Server 2016 Insider Preview Build 16237 was released to Windows Insiders on July 13, 2017.[35][36]
Windows Server 2016 was officially released at Microsoft’s Ignite Conference on September 26, 2016. Unlike its predecessor, Windows Server 2016 is licensed by the number of CPU cores rather than number of CPU sockets—a change that has similarly been adopted by BizTalk Server 2013 and SQL Server 2014.[37] The new licensing structure that has been adopted by Windows Server 2016 has also moved away from the Windows Server 2012/2012R2 CPU socket licensing model in that now the amount of cores covered under one license is limited. Windows Server 2016 Standard and Datacenter core licensing now covers a minimum of 8 core licenses for each physical processor and a minimum of 16 core licenses for each server. Core licenses are sold in packs of two with Standard Edition providing the familiar rights to run 2 virtualized OS environments. If the server goes over 16 core licenses for a 2 processor server additional licenses will now be required with Windows Server 2016.[38]
Windows Server 2016 Technical Preview, released on October 1, 2014, was the first beta version of the operating system made publicly available. Its version number was 6.4.9841.[5]
Technical Preview 2
[edit]
Windows Server 2016 Technical Preview 2 was made available on May 4, 2015. Its version number was 10.0.10074. (A similar jump in the most significant part of the version number from 6 to 10 is seen in Windows 10.) Highlights of this version include:[39]
- Nano Server installation option[40][41]
- Hyper-V: hot add and remove memory and NIC; resilient virtual machines to keep running even when their cluster fabric fails[42]
- Rolling upgrades for Hyper-V and Storage clusters[40][42]
- Networking: Converged NIC across tenant and RDMA traffic; PacketDirect on 40G[42]
- Storage: Virtual Machine Storage Path resiliency; Storage Spaces Direct to aggregate Storage Spaces across multiple servers; Storage Replica[42]
- Security: Host Guardian Service, helping to keep trust and isolation boundary between the cloud infrastructure and guest OS layers; Just Enough Administration, restricting users to perform only specific tasks[42]
- Management: PowerShell Desired State Configuration; PowerShell Package Manager; Windows Management Framework 5.0 April Preview and DSC Resource Kit[42]
- Other: Conditional access control in AD FS; application authentication support for OpenID Connect and OAuth; full OpenGL support with RDS for VDI; Server-side support for HTTP/2, including header compression, connection multiplexing and server push[42]
- Installation options: Minimal Server Interface was made default and renamed the Server installation option to “Server with local admin tools”.[43]
Technical Preview 3
[edit]
The third technical preview of Windows Server 2016 was made available on August 19, 2015. Its version number was 10.0.10514. Highlights of this version include:
- Windows Server Containers[44]
- Active Directory Federation Services (AD FS): authentication of users stored in Lightweight Directory Access Protocol (LDAP) directories[44]
- Installation options: The Server installation option had been renamed to “Server with Desktop Experience” having the shell and Desktop Experience installed by default. Due to the structural changes required to deliver the Desktop Experience on Server, it is no longer possible to convert from Server with Desktop Experience to Server Core or to convert Server Core up to Server with Desktop Experience.[43]
Technical Preview 4
[edit]
The fourth technical preview of the operating system was made available on November 19, 2015, one year and one month after the initial technical preview. Its version number was 10.0.10586, based on Windows 10 version 1511. Its highlights include:
- Nano Server supports the DNS Server and IIS server roles, as well as MPIO, VMM, SCOM, DSC push mode, DCB, Windows Server Installer, and the WMI provider for Windows Update. Its Recovery Console supports editing and repairing the network configuration. A Windows PowerShell module is now available to simplify building Nano Server images.[45]
- Hyper-V Containers encapsulates each container in a light weight virtual machine.[45]
Technical Preview 5
[edit]
The last technical preview of Windows Server 2016 was made available on April 27, 2016. Its version number was 10.0.14300. Its highlights include:[46]
- Mostly general refinements. Greater time accuracy in both physical and virtual machines
- Container support adds performance improvements, simplified network management, and support for Windows containers on Windows 10
- Nano Server: an updated module for building Nano Server images, including more separation of physical host and guest virtual machine functionality as well as support for different Windows Server editions. Improvements to the Recovery Console, including separation of inbound and outbound firewall rules as well as the ability to repair configuration of WinRM
- Networking: traffic to new or existing virtual appliances can now be both mirrored and routed. With a distributed firewall and Network security groups, this enables dynamically segmented and secure workloads in a manner similar to Azure. One can deploy and manage the entire Software-defined networking (SDN) stack using System Center Virtual Machine Manager. Docker can be used to manage Windows Server container networking, and associate SDN policies not only with virtual machines but containers as well
- Remote Desktop Services: a highly available RDS deployment can leverage Azure SQL Database for the RD Connection Brokers in high availability mode
- Management: ability to run PowerShell.exe locally on Nano Server (no longer remote only), new Local Users & Groups cmdlets to replace the GUI, added PowerShell debugging support, and added support in Nano Server for security logging & transcription and JEA (Just Enough Administration)
- Shielded Virtual Machines:
- New «Encryption Supported» mode that offers more protections than for an ordinary virtual machine, but less than «Shielded» mode, while still supporting vTPM, disk encryption, Live Migration traffic encryption, and other features, including direct fabric administration conveniences such as virtual machine console connections and Powershell Direct
- Full support for converting existing non-shielded Generation 2 virtual machines to shielded virtual machines, including automated disk encryption
- Shielded virtual machines are compatible with Hyper-V Replica
Release to manufacturing
[edit]
Windows Server 2016 was released to manufacturing on September 26, 2016, bearing the version number of 10.0.14393 (same as Windows 10 Anniversary Update). Microsoft added the following final touches:
- Available for a 180-day evaluation
- Fixed Start menu corruptions
- Improved user experience and performance
- Windows Store apps have been removed
- Login screen now has a background
- The Windows Hello feature has been added
- Dark theme has been added
Semi-Annual Channel releases
[edit]
Windows Server, version 1709 (version shared with Windows 10 Fall Creators Update) was released on October 17, 2017. The release has dropped the Windows Server 2016 name and is just called Windows Server by Microsoft.[47] It is offered to the Microsoft Software Assurance customers who have an active Windows Server 2016 license and has the same system requirements. This is the first Windows Server product to fall under the «Semi-Annual Channel» (SAC) release cadence.[48] This product only features the Server Core and the Nano Server modes. Of the two, only the Server Core mode of the OS can be installed on a bare system. The Nano Server mode is only available as an operating system container.[49]
Windows Server, version 1803 (version shared with Windows 10 April 2018 Update) is the second Semi-Annual Channel release of Windows Server.[50] It is also the final version to be branched off the Server 2016 codebase, as the next release shares the version number 1809 with Windows Server 2019.[51]
- Microsoft Servers
- Comparison of Microsoft Windows versions
- History of Microsoft Windows
- Comparison of operating systems
- List of operating systems
- ^ a b Chapple, Erin (September 26, 2016). «Announcing the launch of Windows Server 2016». Hybrid Cloud. Microsoft. Archived from the original on August 21, 2017. Retrieved September 27, 2016.
- ^ a b c Foley, Mary Jo (October 12, 2016). «Microsoft’s Windows Server 2016 hits general availability». ZDNet. CBS Interactive. Archived from the original on October 15, 2016. Retrieved October 12, 2016.
- ^ «April 11, 2025—KB5058921 (OS Build 14393.7973) Out-of-band». Microsoft Support. Microsoft.
- ^ «Windows Server 2016 — Microsoft Lifecycle». Microsoft Learn. Microsoft. Retrieved February 17, 2025.
- ^ a b «Announcing availability of Windows Server Technical Preview and System Center Technical Preview». Hybrid Cloud. Microsoft. March 17, 2015. Archived from the original on August 2, 2017. Retrieved April 1, 2015.
- ^ Mathers, Bill; Poggemeyer, Liza; Tobin, John (September 8, 2017). «What’s new in Active Directory Federation Services for Windows Server 2016». Microsoft Docs. Windows Server, Identity and access. Archived from the original on February 28, 2018. Retrieved January 22, 2018.
- ^ «TechNet: Windows Server Antimalware Overview for Windows Server Technical Preview (Updated: 19 February 2015)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in Remote Desktop Services in the Windows Server Technical Preview (Updated: 1 October 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in Storage Services in Windows Server Technical Preview (Updated: 1 October 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in Failover Clustering in Windows Server Technical Preview (Updated: 1 October 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in Web Application Proxy in Windows Server Technical Preview (Updated: 1 October 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ O’Shea, Mark (September 4, 2016). «What’s New In Windows Server 2016 Standard Edition Part 9 – Management And Automation». Microsoft Australia OEM Team blog. Microsoft. Archived from the original on September 17, 2016. Retrieved September 9, 2016.
- ^ «About Windows Containers». Archived from the original on November 4, 2016. Retrieved November 1, 2016.
- ^ «TechNet: What’s New in DHCP in Windows Server Technical Preview (Updated: 1 October 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in DNS Client in Windows Server Technical Preview (Updated: 1 October 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in DNS Server in Windows Server Technical Preview (Updated: 1 October 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: GRE Tunneling in Windows Server Technical Preview (Updated: 1 October 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in IPAM in Windows Server Technical Preview (Updated: 6 February 2015)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: Network Controller (Updated: 18 December 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in Hyper-V Network Virtualization in Windows Server Technical Preview (Updated: 11 March 2015)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet: What’s New in Hyper-V in Technical Preview (Updated: 12 November 2014)». Archived from the original on April 9, 2015. Retrieved April 4, 2015.
- ^ «TechNet Wiki: Hyper-V Features in Windows Server 2016». Archived from the original on March 12, 2016. Retrieved March 12, 2016.
- ^ «Remote Direct Memory Access (RDMA) and Switch Embedded Teaming (SET)». Microsoft. May 17, 2016. Archived from the original on August 10, 2016. Retrieved July 6, 2016.
- ^ Jindal, Kriti (February 9, 2016). «Introducing Server management tools». Nano Server Blog. Microsoft.
- ^ Neil, Mike (April 8, 2015). «Microsoft Announces New Container Technologies for the Next Generation Cloud». Server & Cloud Blog. Microsoft. Archived from the original on September 27, 2016. Retrieved September 27, 2016.
- ^ Snover, Jeffrey; Mason, Andrew; Back, Alan (April 8, 2015). «Microsoft Announces Nano Server for Modern Apps and Cloud». Windows Server Blog. Microsoft. Archived from the original on August 19, 2016. Retrieved July 24, 2016.
- ^ «Changes to Nano Server in the next release of Windows Server». Archived from the original on January 27, 2018. Retrieved June 18, 2017.
- ^ Patrizio, Andy (February 10, 2015). «Microsoft to release next generation of Windows Server in 2016». Network World. IDG. Archived from the original on April 26, 2024. Retrieved April 10, 2015.
- ^ Vincent, James (March 9, 2017). «Microsoft unveils new ARM server designs, threatening Intel’s dominance». The Verge. Vox Media. Archived from the original on December 23, 2017. Retrieved September 18, 2017.
- ^ Foley, Mary Jo (March 8, 2017). «Windows Server on ARM: It’s happening». ZDNet. CBS Interactive. Archived from the original on March 10, 2017. Retrieved March 10, 2017.
- ^ Bright, Peter (March 8, 2017). «Microsoft’s latest open source servers shown off with Intel, AMD, and even ARM chips». Ars Technica. Condé Nast. Archived from the original on March 10, 2017. Retrieved March 10, 2017.
- ^ Foley, Mary Jo (March 10, 2017). «Microsoft’s Windows Server on ARM move: More questions and answers». ZDNet. CBS Interactive. Archived from the original on March 11, 2017. Retrieved March 11, 2017.
- ^ «Windows IT Pro: Windows Server Technical Preview expires 15 April 2015». Archived from the original on April 10, 2015. Retrieved April 5, 2015.
- ^ «Neowin: Second tech preview of Windows Server 2016 coming next month». Archived from the original on April 5, 2015. Retrieved April 5, 2015.
- ^ «RedmondMag: Windows Server ‘Insider’ Testing Program Coming This Summer». Archived from the original on August 5, 2017. Retrieved May 14, 2017.
- ^ «Announcing Windows Server Insider Preview Build 16237». Windows Blog. Microsoft. July 13, 2017. Archived from the original on December 3, 2017. Retrieved July 24, 2017.
- ^ Bright, Peter (December 4, 2015). «Windows Server 2016 moving to per core, not per socket, licensing». Ars Technica. Condé Nast. Archived from the original on December 4, 2015. Retrieved December 5, 2015.
- ^ Microsoft (2017). «Windows Server 2016 Licensing Datasheet — Microsoft» (PDF). Microsoft. Archived (PDF) from the original on October 26, 2017. Retrieved October 8, 2017.
- ^ Berkouwer, Sander (May 5, 2015). «Windows Server 2016 Technical Preview 2 now available». The things that are better left unspoken. Archived from the original on April 6, 2016. Retrieved March 26, 2016.
- ^ a b «The Register: Try to contain your joy: Microsoft emits Windows Server 2016 with nano-services». The Register. Archived from the original on September 11, 2017. Retrieved September 18, 2017.
- ^ «WinBeta: Microsoft shows off what’s new in Windows Server 2016 Technical Preview 2». May 4, 2015. Archived from the original on May 5, 2015. Retrieved May 5, 2015.
- ^ a b c d e f g «Windows Server Blog: What’s new in Windows Server 2016 Technical Preview 2». Archived from the original on May 7, 2015. Retrieved May 5, 2015.
- ^ a b «Windows Server Blog: Windows Server 2016 Installation Option Changes». August 27, 2015. Archived from the original on November 11, 2016. Retrieved November 11, 2016.
- ^ a b «TechNet: What’s New in Windows Server 2016 Technical Preview 3». Archived from the original on September 6, 2015. Retrieved August 19, 2015.
- ^ a b Anderson, Kareem (November 19, 2015). «Microsoft has released Windows Server 2016 Technical Preview 4». WinBeta. Archived from the original on November 23, 2015. Retrieved November 20, 2015.
- ^ «TechNet: What’s New in Windows Server 2016 Technical Preview 5». Archived from the original on June 3, 2016. Retrieved April 27, 2016.
- ^ «Windows Server, version 1709 available for download». October 17, 2017. Archived from the original on November 7, 2017. Retrieved November 1, 2017.
- ^ Jawad, Usama (September 25, 2017). «Microsoft launches Windows Server version 1709». Neowin. Archived from the original on March 13, 2018. Retrieved March 12, 2018.
- ^ «Introducing Windows Server, version 1709». Microsoft Docs. Microsoft. Windows Server. Archived from the original on January 21, 2018. Retrieved January 21, 2018.
- ^ «Windows Server servicing channels». Archived from the original on November 15, 2018. Retrieved November 15, 2018.
- ^ «Windows 10 and Windows Server 2019 update history». Archived from the original on December 18, 2019. Retrieved November 15, 2018.
-
Home
-
News
- When Is Windows Server 2016 End of Life? How to Upgrade?
By Vera | Follow |
Last Updated
What is the end of life for Windows Server 2016? How can you upgrade to Server 2022 after Server 2016 EOL? In this post, MiniTool will tell you answers to these questions and countermeasures. Now, let’s have a look.
Windows Server 2016 End of Life
Server 2016 is the eighth release of the Microsoft Windows Server operating system and it was developed along with Windows 10. On October 1, 2014, its first preview version appeared. On Sep 26, 2016, Server 2016 was released and then broadly released for retail sale on Oct 12, 2016.
Now Windows Server 2022 has come for several years, and then you may ask: is Windows Server 2016 end of support? Generally, each operating system has its lifecycle. Speaking of Server 2016 end of life, Microsoft ended its Mainstream Support on Jan 11, 2022.
After that date, the system won’t receive some updates but security updates are still available. Besides, Server 2016 won’t receive any bug fixes or improvements.
But after the Mainstream end date, you can choose to purchase Extended Security Update (ESU) to gain Extended Support which is usually 5 years. When it comes to “Windows Server 2016 end of life extended support”, its end date refers to Jan 12, 2027. That is, the final Server 2016 EOL lasts until Jan 12, 2027.
The two dates here apply to these editions of the Server system, including Datacenter, Essentials, MultiPoint Premium, and Standard.
Upgrade to Windows Server 2022 from 2016
As this operating system ages, it is liable to virus attacks or other malicious software from cybercriminals. Eventually, manufacturers cannot patch and update the old system because of outdated architecture. So to protect your data from various attacks and prevent data loss, upgrade your Windows Server 2016 to 2022 after Server 2016 end of life.
Back up Files in Server
Before the update, we recommend you to back up your important files in Server 2016 since you may run into some update issues or errors, leading to data loss. To prevent file loss, run the backup software – MiniTool ShadowMaker for data backup. Besides, if you use an ISO file to perform a clean install of the Server system, we also advise you to backup files since this installation process can erase your C drive including files saved in it.
MiniTool ShadowMaker enables you to easily backup files, folders, disks, partitions, and Windows, and its Trial Edition can work well in Windows 11/10/8/8.1/7 and Windows Server 2022/2019/2016/2012/2008. Now, download and install it on your Server 2016 for data backup.
MiniTool ShadowMaker TrialClick to Download100%Clean & Safe
Step 1: Launch MiniTool ShadowMaker Trial Edition and connect a USB drive or external hard drive to the PC.
Step 2: Go to Backup > SOURCE > Folders and Files, choose files to back up, and click OK.
Step 3: In Backup, click SOURCE to choose an external drive or USB drive.
Step 4: Click Back Up Now to begin file backup.
How to Upgrade to Server 2022 After Windows Server End of Life
After the backup, now you can choose to upgrade to Windows Server 2022 and here we take an in-place upgrade as an example:
Step 1: Download Windows Server 2022 ISO and save it on the Desktop.
Step 2: Right-click on the ISO and choose Mount.
Step 3: Double-click on the setup.exe file and then the Windows Server Setup window opens. Tap on Next to continue.
Step 4: Choose an edition of Windows Server 2022.
Step 5: Finish the update by following the on-screen instructions.
Tips:
If you want to clean install Windows Server 2022 from 2016, go to see this guide — How to Install, Set up, and Configure Windows Server 2022.
Final Words
In light of Windows Server 2016 end of life (EOL), you should take action to upgrade to an up-to-date version. To keep data safe, you had better back up crucial files before the update. Besides, if the PC is not suitable for the upgrade, it is also essential to back up data to safeguard against data loss or corruption resulting from system crashes using MiniTool ShadowMaker.
MiniTool ShadowMaker TrialClick to Download100%Clean & Safe
About The Author
Position: Columnist
Vera is an editor of the MiniTool Team since 2016 who has more than 7 years’ writing experiences in the field of technical articles. Her articles mainly focus on disk & partition management, PC data recovery, video conversion, as well as PC backup & restore, helping users to solve some errors and issues when using their computers. In her spare times, she likes shopping, playing games and reading some articles.
Visual representation of the migration process from Windows Server 2016 to modern platforms, highlighting assessment, migration, and validation steps
Introduction
Windows Server 2016 has been a reliable and powerful operating system for businesses worldwide. However, as with all software, it follows a lifecycle, and its End of Life (EOL) is approaching. Understanding the EOL process is essential for maintaining a secure and compliant IT environment. This guide explains what Windows Server 2016 EOL means, the risks of using unsupported software, and how to prepare for the transition to newer systems.
Understanding the Lifecycle of Windows Server 2016
Release and Support Timeline
Windows Server 2016 was officially released on October 12, 2016. Microsoft provides support in two phases:
- Mainstream Support: Ended on January 11, 2022. This phase included feature updates, security patches, and complimentary support.
- Extended Support: Will end on January 12, 2027. During this phase, only critical security updates are provided, with no new features or free support.
Once the Extended Support phase ends, no updates—security or otherwise—will be provided. This marks the EOL, leaving systems vulnerable to security threats.
Mainstream vs. Extended Support
| Support Type | Features Provided |
|---|---|
| Mainstream Support | Feature updates, security patches, free support |
| Extended Support | Security updates only, no feature updates or free support |
Why the EOL Matters
When Windows Server 2016 reaches EOL, businesses still using it will face significant challenges, including:
- No more security updates, exposing systems to malware and cyber-attacks.
- Potential non-compliance with regulatory standards.
- Compatibility issues with modern software.
Risks of Using Unsupported Software
Security Vulnerabilities
Without regular updates, unsupported software becomes a target for cybercriminals. Known vulnerabilities will remain unpatched, increasing the risk of:
- Data breaches
- Malware infections
- Ransomware attacks
Compliance Issues
Many industries have strict compliance standards (e.g., GDPR, HIPAA) that require up-to-date systems. Using unsupported software may result in:
- Fines for non-compliance
- Loss of certifications
- Damage to your business reputation
Operational Challenges
Unsupported systems may struggle with:
- Compatibility issues when integrating with new hardware or software
- Higher maintenance costs
- Decreased efficiency and productivity
Preparing for the Transition
Step 1: Assess Your Current Infrastructure
Begin by conducting a thorough assessment:
- Create an inventory of all Windows Server 2016 deployments.
- Identify dependencies, including applications, databases, and hardware.
Step 2: Identify Upgrade Paths
Options include:
- Upgrading to Windows Server 2019 or Windows Server 2022.
- Migrating to a cloud-based solution such as Microsoft Azure.
Step 3: Plan the Migration
Develop a detailed migration plan:
- Allocate resources and define timelines.
- Test the new environment before full deployment.
- Ensure all data is securely backed up.
Exploring Upgrade Options
Windows Server 2019
Windows Server 2019 offers several improvements over its predecessor, including:
- Enhanced security features like Shielded Virtual Machines.
- Improved hybrid cloud capabilities.
- Support for Kubernetes.
Windows Server 2022
The latest version, Windows Server 2022, introduces:
- Advanced multilayered security, including Secured-core server.
- Improved scalability and performance.
- Seamless cloud integration with Azure Arc.
Cloud Migration
Migrating to cloud solutions like Microsoft Azure provides:
- Scalability and flexibility.
- Built-in security and compliance.
- Reduced infrastructure costs.
Step-by-Step Migration Guide
Pre-Migration Checklist
- Back up all critical data and system configurations.
- Check application and hardware compatibility with the new system.
Migration Process
- Set up the new environment: Install and configure the new server or cloud environment.
- Transfer data and roles: Migrate files, applications, and server roles.
- Test and validate: Ensure everything functions correctly before decommissioning old servers.
Post-Migration Tasks
- Monitor system performance.
- Apply any required patches or updates.
- Decommission legacy systems securely.
Best Practices for Future-Proofing Your IT Infrastructure
Regular Updates
Stay proactive by updating systems regularly to ensure security and performance.
Security Measures
Implement robust cybersecurity measures such as firewalls, intrusion detection systems, and regular audits.
Asset Management
Develop a strategy for managing IT assets, including lifecycle planning and regular reviews.
Plan for Upgrades
Anticipate future EOL dates and plan migrations well in advance to avoid last-minute disruptions.
FAQs
- What happens if I continue using Windows Server 2016 after its EOL? Continuing to use unsupported software exposes your systems to significant security and compliance risks.
- Can I purchase Extended Security Updates (ESUs) beyond January 2027? Microsoft typically offers ESUs for a limited time after EOL, but these come at a cost and may not be available indefinitely.
- How do I choose between upgrading and migrating to the cloud? Consider factors like budget, scalability, and operational requirements. Cloud solutions offer flexibility, while on-premises upgrades may provide greater control.
- What are the costs associated with upgrading? Costs vary based on licensing, hardware upgrades, and migration services. Conduct a cost analysis to understand your total investment.
- Can I run a mix of Windows Server versions in my environment? Yes, but ensure compatibility between versions and plan for eventual consolidation.
Additional FAQs
- Is Windows Server 2016 still secure during Extended Support? Yes, but only critical security updates are provided, and no new features are added.
- What tools can assist with migration? Microsoft offers tools like the Windows Server Migration Tools and Azure Migrate.
- How long does a typical migration take? Depending on complexity, migrations can take weeks to months. Plan accordingly.
- Can third-party software extend support for Windows Server 2016? Some vendors offer extended support services, but they may not meet all security and compliance standards.
- What training is needed for staff during a migration? Ensure IT teams are trained on the new environment and have access to resources for troubleshooting and management.
Conclusion
Windows Server 2016 End of Life is a critical milestone that businesses cannot afford to overlook. By understanding the lifecycle, assessing risks, and planning for upgrades or migrations, you can ensure a secure and compliant IT environment. Take proactive steps today to future-proof your systems and stay ahead in an ever-evolving technological landscape.
Other Articles
LBX CentBrowser 1.6: A Comprehensive Guide
Skyward189: The Ultimate Comprehensive Guide
Comprehensive Guide to VF1H-1 50MHz Oscillator
Exploring the Significance of 2602063827: An In-Depth Guide