If the DHCP server is running Windows Server 2016, these requests are processed as if no SoH is present. DHCP client computers that are also NAP clients send a statement of health (SoH) with the DHCP request. In Windows Server 2016, DHCP servers do not enforce NAP policies, and DHCP scopes cannot be NAP-enabled. For more information about DHCP in NAP, see Checklist: Implementing a DHCP Enforcement Design. In a NAP deployment, a DHCP server running an operating system that supports NAP can function as a NAP enforcement point for the NAP DHCP enforcement method. The following table summarizes support for NAP in Windows Server.
NAP support was introduced to the DHCP Server role with Windows Server 2008, and is supported in Windows client and server operating systems prior to Windows 10 and Windows Server 2016. For more information, see Features Removed or Deprecated in Windows Server 2012 R2. Network Access Protection (NAP) is deprecated in Windows Server 2012 R2, and in Windows Server 2016 the DHCP Server role no longer supports NAP. DHCP NAP Is Not Supported in Windows Server 2016
New Logging Events for DNS Registration Failures by the DHCP ServerĭHCP now includes logging events for circumstances in which DHCP server DNS record registrations fail on the DNS server.įor more information, see DHCP Logging Events for DNS Record Registrations. If you are using a DHCP relay agent that is configured with DHCP option 82, sub-option 5, the relay agent can request an IP address lease for DHCP clients from a specific IP address range.įor more information, see DHCP Subnet Selection Options. You can use this option to allow DHCP proxy clients and relay agents to request an IP address for a specific subnet. DHCP Subnet Selection OptionsĭHCP now supports option 82 (sub-option 5). DHCP option 119 is specified in RFC 3397. The Domain Search Option provides DNS suffixes for DNS lookups of short names.
The DHCP client in Windows 10 has been updated in the Windows April 2018 Update (also referred to as Windows 10, version 1803) to read in and apply option 119, the Domain Search Option, from the DHCP server that your system connects to. New DHCP Client-side features in the Windows 10 April 2018 Update Some devices will now show up as MSFT 5.0 XBOX. Note that not all Android tethered phones will be detected as metered, and some other networks may also show up as metered.Īdditionally, the traditional Client Vendor Name has been updated for some Windows-based devices. Previously, the connections were marked as unmetered. When you're running a Windows client and connect to the internet via a tethered Android phone, the connection should be marked as "metered". The DHCP client in Windows 10 has been updated in the Update (also referred to as Windows 10, version 2004). New DHCP Client-side features in the Windows Update The following sections provide information about new features and changes in functionality for DHCP. By using the DHCP Server service, the process of configuring TCP/IP on DHCP clients is automatic. This topic describes the Dynamic Host Configuration Protocol (DHCP) functionality that is new or changed in Windows Server 2016.ĭHCP is an Internet Engineering Task Force (IETF) standard that is designed to reduce the administrative burden and complexity of configuring hosts on a TCP/IP-based network, such as a private intranet. Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016