From Wikipedia, the free encyclopedia
| 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; 6 years ago[1] |
| General availability |
October 12, 2016; 6 years ago[2] |
| Latest release | 1607 (10.0.14393.6252) (September 12, 2023; 13 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) / Windows Server, version 1709 (2017) |
| Official website | Windows Server 2016 (archived at Wayback Machine) |
| Support status | |
|
Windows Server 2016 is the eighth release of the Windows Server operating system developed by Microsoft as part of the Windows NT family of operating systems. 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 broadly released for retail sale on October 12, 2016.[2] It was succeeded by Windows Server 2019 and the Windows Server Semi-Annual Channel.
Features[edit]
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]
Hyper-V[edit]
- 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]
Nano Server[edit]
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]
Development[edit]
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]
Preview releases[edit]
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]
Public release[edit]
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]
Version history[edit]
Technical Preview[edit]
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]
Version 1709[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]
Version 1803[edit]
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]
See also[edit]
- Microsoft Servers
- Comparison of Microsoft Windows versions
- History of Microsoft Windows
- Comparison of operating systems
- List of operating systems
References[edit]
- ^ 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.
- ^ «September 12, 2023—KB5030213 (OS Build 14393.6252)». Microsoft Support. Microsoft.
- ^ «Microsoft Product Lifecycle». Microsoft Support. Microsoft. Archived from the original on October 2, 2019. Retrieved December 7, 2016.
- ^ 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 March 21, 2015. 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». 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.
External links[edit]
- PluralSight: Windows Server vNext First Look – An introduction to the new features of the Windows Server vNext operating system
- Our Server Journey – video session describing the path that Windows Server has taken from its creation to the current day and where it is going from here Archived April 9, 2015, at the Wayback Machine
- Michael Pietroforte: Nano Server – Goodbye Windows Server?
- Microsoft Windows Nano Server, the future of Windows Server?
Windows Server (formerly Windows NT Server) is a group of operating systems (OS) for servers by
Microsoft. The brand name was changed to Windows Server in 2003.
| Release | Released | Active Support | Security Support | Extended Security Updates | Latest |
|---|---|---|---|---|---|
|
Windows Server 2022 (LTSC) |
2 years ago
(18 Aug 2021) |
Ends (13 Oct 2026) |
Ends (14 Oct 2031) |
Unavailable |
10.0.20348 |
|
Windows Server 20H2 |
2 years and 11 months ago
(20 Oct 2020) |
Ended (09 Aug 2022) |
Ended (09 Aug 2022) |
Unavailable |
10.0.19042 |
|
Windows Server 2004 |
3 years and 4 months ago
(27 May 2020) |
Ended (14 Dec 2021) |
Ended (14 Dec 2021) |
Unavailable |
10.0.19041 |
|
Windows Server 1909 |
3 years and 11 months ago
(12 Nov 2019) |
Ended (11 May 2021) |
Ended (11 May 2021) |
Unavailable |
10.0.18363 |
|
Windows Server 1809 |
4 years and 11 months ago
(13 Nov 2018) |
Ended (10 Nov 2020) |
Ended (10 Nov 2020) |
Unavailable |
10.0.17763 |
|
Windows Server 2019 (LTSC) |
4 years and 11 months ago
(13 Nov 2018) |
Ends (09 Jan 2024) |
Ends (09 Jan 2029) |
Unavailable |
10.0.17763 |
|
Windows Server 1903 |
5 years ago
(21 May 2018) |
Ended (08 Dec 2020) |
Ended (08 Dec 2020) |
Unavailable |
10.0.18362 |
|
Windows Server 1803 |
5 years ago
(30 Apr 2018) |
Ended (12 Nov 2019) |
Ended (12 Nov 2019) |
Unavailable |
10.0.17134 |
|
Windows Server 1709 |
5 years and 11 months ago
(17 Oct 2017) |
Ended (09 Apr 2019) |
Ended (09 Apr 2019) |
Unavailable |
10.0.16299 |
|
Windows Server 2016 (LTSC) |
6 years and 12 months ago
(15 Oct 2016) |
Ended (11 Jan 2022) |
Ends (12 Jan 2027) |
Unavailable |
10.0.14393 |
|
Windows Server 2012-R2 (LTSC) |
9 years ago
(25 Nov 2013) |
Ended (09 Oct 2018) |
Ends (10 Oct 2023) |
Ends (13 Oct 2026) |
6.3.9600 |
|
Windows Server 2012 (LTSC) |
10 years ago
(30 Oct 2012) |
Ended (09 Oct 2018) |
Ends (10 Oct 2023) |
Ends (13 Oct 2026) |
6.2.9200 |
|
Windows Server 2008-R2-SP1 (LTSC) |
12 years ago
(22 Feb 2011) |
Ended (13 Jan 2015) |
Ended (14 Jan 2020) |
Ended (10 Jan 2023) |
6.1.7601 |
|
Windows Server 2008-SP2 (LTSC) |
14 years ago
(29 Apr 2009) |
Ended (13 Jan 2015) |
Ended (14 Jan 2020) |
Ended (10 Jan 2023) |
6.0.6003 |
|
Windows Server 2003-SP2 (LTSC) |
20 years ago
(24 Apr 2003) |
Ended (13 Jul 2010) |
Ended (14 Jul 2015) |
Unavailable |
5.2.3790 |
|
Windows Server 2000 (LTSC) |
23 years ago
(17 Feb 2000) |
Ended (30 Jun 2005) |
Ended (13 Jul 2010) |
Unavailable |
5.0.2195 |
Servicing channels
Previously with Windows Server 2016 and Windows Server 2019 there have been two primary release channels available:
- Long-Term Servicing Channel (LTSC)
- Semi-Annual Channel (SAC)
The Windows Server Semi-Annual Channel (SAC) was retired on August 9, 2022. There will be no future SAC releases of Windows Server.
Long-Term Servicing Channel (LTSC)
With the Long-Term Servicing Channel, a new major version of Windows Server is released every 2-3 years. Users are entitled to 5 years of mainstream support and 5 years of extended support. The Long-Term Servicing Channel will continue to receive security and non-security updates, but it will not receive the new features and functionality.
Semi-Annual Channel (SAC)
Each release in this channel is supported for 18 months from the initial release. Most of the features introduced in the Semi-Annual Channel have been rolled up into the next Long-Term Servicing Channel release of Windows Server.
In this model, Windows Server releases were identified by the year and month of release: for example, in 2017, a release in the 9th month (September) would be identified as version 1709. Fresh releases of Windows Server in the Semi-Annual Channel occurred twice each year. The support lifecycle for each release is 18 months. Starting with fall 2020 (20H2) releases, the identification changed. Instead of a month, the release is named based on the release cycle. For example: version 20H2, for a release in the second half of the year 2020.
Extended Security Updates (ESU)
For some releases, customers also have the option to purchase Extended Security Updates (ESU).
It includes Critical and/or Important security updates for a maximum of three years after the
product’s End of Extended Support date. Customers can also get technical support for the ESU period
as long as they also have an active support plan.
More information is available on the Microsoft Windows Server website.
You should be running one of the supported release numbers listed above in the rightmost column.
You can check the version that you are currently using by running:
winver
You can submit an improvement to this page
on GitHub
.
This page has a corresponding
Talk Page.
A JSON version of this page is available at /api/windows-server.json.
See the API Documentation for more information.
You can subscribe to the iCalendar feed at /calendar/windows-server.ics.
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
Hello Dev, if you are reading this article, it’s likely you are a developer or IT professional responsible for managing Windows Server 2016 environment. As you may know, the Windows Server 2016 has reached its end of life stage, which means it will no longer receive security updates, bug fixes, or technical support from Microsoft. In this guide, we will explain what Windows Server 2016 end of life means for you and your organization, as well as provide recommendations and solutions to help you navigate this transition.
What Does Windows Server 2016 End of Life Mean?
Windows Server 2016 was released in September 2016 as the successor to Windows Server 2012. Like all Microsoft products, Windows Server 2016 had a lifecycle. The lifecycle of a product usually consists of two phases: mainstream support and extended support.
Microsoft provided mainstream support for Windows Server 2016 until January 2022. During that period, Microsoft provided regular updates, including feature improvements, security patches, and bug fixes, as well as technical support to customers who faced issues with the product.
However, as of January 2022, Windows Server 2016 has entered the extended support phase, which means it will no longer receive feature updates, and Microsoft will only provide security updates and technical support for a limited time.
Here’s what you need to know about the Windows Server 2016 end of life:
|
End of mainstream support |
January 11, 2022 |
|
End of extended support |
January 11, 2027 |
|
Security updates |
Provided until January 11, 2027 |
|
Technical support |
Provided until January 11, 2027 |
After January 11, 2027, Microsoft will no longer provide technical support or security updates for Windows Server 2016, leaving your environment open to vulnerabilities, compatibility issues, and potential downtime.
What are the Risks of Running Windows Server 2016 After End of Life?
If you continue to run Windows Server 2016 after end of life, you should be aware of the following risks:
- Security vulnerabilities: As Microsoft will no longer provide security updates, any vulnerabilities found in Windows Server 2016 will remain unpatched, making your environment vulnerable to attacks.
- Compliance issues: Running an unsupported operating system can cause compliance issues, especially if you are in a regulated industry such as finance, healthcare, or government.
- Compatibility issues: As newer software and hardware are released, they may no longer be compatible with Windows Server 2016, leading to potential downtime or costly upgrades.
- Limited technical support: Microsoft will no longer provide technical support for Windows Server 2016 after end of life, leaving you on your own to troubleshoot any issues that arise.
What are Your Options After Windows Server 2016 End of Life?
As you can see, running Windows Server 2016 after end of life is not a viable option for most IT environments. Here are some options available to you:
Upgrade to a Supported Version of Windows Server
The most straightforward option is to upgrade to a newer, supported version of Windows Server. This will ensure you receive regular updates, security patches, and technical support from Microsoft. There are several versions of Windows Server available, each with their own set of features and licensing options.
Some of the newer versions of Windows Server include:
- Windows Server 2019
- Windows Server 2022
Before upgrading to a new version of Windows Server, you should evaluate your environment to ensure compatibility with your existing applications, hardware, and network infrastructure. You should also consider licensing requirements and the costs of the upgrade.
Move to the Cloud
Another option is to move your IT infrastructure to the cloud, using services such as Microsoft Azure, Amazon Web Services (AWS), or Google Cloud Platform. Cloud services offer several benefits, including scalability, cost savings, and built-in security features.
When moving to the cloud, you should evaluate your existing workloads and determine which applications and services are best suited for the cloud. You should also consider the costs of the cloud provider and any migration or integration issues that may arise.
Migrate to Linux
If you’re looking for a more cost-effective and open-source alternative to Windows Server, Linux may be a viable option for your organization. Linux is a free, open-source operating system that offers a high degree of customization and flexibility.
When migrating to Linux, you should evaluate your existing applications and determine which can be migrated to Linux. You should also consider the costs of training and support for Linux, as well as the availability of Linux-based tools and applications that will be required in your environment.
Frequently Asked Questions About Windows Server 2016 End of Life
Q: What happens if I continue to run Windows Server 2016 after end of life?
If you continue to run Windows Server 2016 after end of life, you will no longer receive security updates or technical support from Microsoft. This can leave your environment vulnerable to security breaches and compatibility issues.
Q: When did Windows Server 2016 reach end of life?
Windows Server 2016 reached end of mainstream support on January 11, 2022. It will reach end of extended support on January 11, 2027.
Q: What are my options after Windows Server 2016 end of life?
Your options after Windows Server 2016 end of life include upgrading to a newer version of Windows Server, moving to the cloud, or migrating to Linux. You should evaluate each option based on your environment, needs, and budget.
Q: What should I consider before upgrading to a new version of Windows Server?
Before upgrading to a new version of Windows Server, you should evaluate your environment to ensure compatibility with your existing applications, hardware, and network infrastructure. You should also consider licensing requirements and the costs of the upgrade.
Q: What are the benefits of moving to the cloud?
Moving to the cloud offers several benefits, including scalability, cost savings, and built-in security features. Cloud services also offer greater flexibility in terms of deploying and managing applications and services.
Q: Is Linux a viable alternative to Windows Server?
Linux is a viable alternative to Windows Server, as it offers a high degree of customization and flexibility at a lower cost. However, migrating to Linux requires careful evaluation of your existing applications and support requirements.
Conclusion
Windows Server 2016 end of life is a critical milestone that requires attention from IT professionals and developers alike. Continuing to run Windows Server 2016 after end of life can lead to security vulnerabilities, compliance issues, and compatibility challenges. However, there are several options available, such as upgrading to a newer version of Windows Server, moving to the cloud, or migrating to Linux. Whatever option you choose, careful evaluation and planning are key to a successful transition.
You’ve probably been seeing a lot about end of support (EoS) for Windows Server 2008 lately. It’s big news, so we couldn’t blame you if you missed the fact that Windows Server 2016 has reached end of life (EoL) and will be considered obsolete at the end of November 2019.
There’s no need to fear. EoL simply means that Microsoft® has released a newer version—so it’s time to say goodbye to Windows Server 2016 OEM licensing from HPE—and hello to Windows Server 2019.
The last day HPE shipped any Windows Server 2016 products was 31 October 2019, though units sent to a distributor or reseller Partner may still be available for purchase after that date. But if you’re running HPE OEM Windows Server 2016 Essentials, Windows Server 2016 Standard, or Windows Server 2016 Datacenter editions, Microsoft will support them through 2027.
If you’re looking to upgrade from Windows Server 2008, it pays to consider Windows Server 2019 on HPE ProLiant Gen10 servers. HPE OEM Windows Server 2019 licenses offer many advantages over other licensing types: they are affordable, customized, and optimized for HPE ProLiant servers, and they include 90 days of free HPE setup support.
When you pair Windows Server 2019 with HPE ProLiant Gen10 servers, you’ll benefit from next-level computing speeds and increased storage capacity, helping your businesses do more, faster—with better insights and performance. Plus, HPE and Microsoft have added cutting-edge security measures to the server and operating system to protect you from cyberthreats and help you maintain data security and compliance.
Still not quite ready to make the switch? HPE OEM Windows Server 2019 licenses come with downgrade rights. This means you can purchase the Windows Server 2019 license and then downgrade it to Windows Server 2016 until you’re ready to use Windows Server 2019.
Visit our alliance page for more details on product versions and which one is the best choice for you.
Willa Anderson
Hewlett Packard Enterprise
twitter.com/CoffeeCoaching
linkedin.com/groups/3413248/
hpe.com/info/CoffeeCoaching