Windows Server 2016
Windows Server 2016 is the seventh release of the Windows Server server operating system developed by Microsoft as part of the Windows NT family of operating systems. It was developed concurrently with Windows 10 and is the successor to Windows Server 2012 R2. The first early preview version became available on October 1, 2014 together with the first technical preview of System Center. Windows Server 2016 was released on September 26, 2016 at Microsoft's Ignite conference and broadly released for retail sale on October 12, 2016. It has two successors: Windows Server 2019, and the Windows Server [|Semi-Annual Channel], which excludes the graphical user interface and many older components.
Features
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 directories and SQL databases.
- Windows Defender: Windows Server Antimalware is installed and enabled by default without the GUI, which is an installable Windows feature.
- Remote Desktop Services: Support for OpenGL 4.4 and OpenCL 1.1, performance and stability improvements; MultiPoint Services role
- Storage Services: Central Storage QoS Policies; Storage Replicas. 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
- 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
- IIS 10: Support for HTTP/2
- Windows PowerShell 5.1
- Windows Server Containers
Networking features
- DHCP: As Network Access Protection was deprecated in Windows Server 2012 R2, in Windows Server 2016 the DHCP role no longer supports NAP
- DNS:
- * DNS client: Service binding – enhanced support for computers with more than one network interface
- * DNS Server: DNS policies, new DDS record types, new PowerShell cmdlets and parameters
- Windows Server Gateway now supports Generic Routing Encapsulation tunnels
- IP address management : 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 Management
- Network Controller: A new server role to configure, manage, monitor, and troubleshoot virtual and physical network devices and services in the datacentre
- Hyper-V Network virtualization: Programmable Hyper-V switch ; VXLAN encapsulation support; Microsoft Software Load Balancer interoperability; better IEEE Ethernet standard compliance.
Hyper-V
- 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.
- Storage quality of service 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
- 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 and memory
- 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.
- RDMA compatible Virtual Switch
Nano Server
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.
Nano Server is only available to Microsoft Software Assurance customers 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.
Development
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.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. 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.
Preview releases
A public beta version of Windows Server 2016 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 Microsoft later released a tool to extend the expiry date, to last until the second tech preview of the OS in May 2015. 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.
Public release
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. 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.Version history
Technical Preview
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.Technical Preview 2
Windows Server 2016 Technical Preview 2 was made available on May 4, 2015. Its version number was 10.0.10074. Highlights of this version include:- Nano Server installation option
- Hyper-V: hot add and remove memory and NIC; resilient virtual machines to keep running even when their cluster fabric fails
- Rolling upgrades for Hyper-V and Storage clusters
- Networking: Converged NIC across tenant and RDMA traffic; PacketDirect on 40G
- Storage: Virtual Machine Storage Path resiliency; Storage Spaces Direct to aggregate Storage Spaces across multiple servers; Storage Replica
- 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
- Management: PowerShell Desired State Configuration; PowerShell Package Manager; Windows Management Framework 5.0 April Preview and DSC Resource Kit
- 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
- Installation options: Minimal Server Interface was made default and renamed the Server installation option to “Server with local admin tools”.
Technical Preview 3
- Windows Server Containers
- Active Directory Federation Services : authentication of users stored in Lightweight Directory Access Protocol directories
- 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.
Technical Preview 4
- 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.
- Hyper-V Containers encapsulates each container in a light weight virtual machine.
Technical Preview 5
- 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 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, 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
- 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
- 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