Tip of the Day: What’s new in the Windows Server 2016 DHCP Server Service

Today’s Tip…

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. Though Network Access Protection (NAP) was officially deprecated in Windows Server 2012 R2 the DHCP server role still supported NAP policies. In Windows Server 2016, DHCP servers will not enforce NAP policies, and DHCP scopes cannot be NAP-enabled.

Nap-capable DHCP client computers will still send a statement of health (SoH) with the DHCP request, however:

  • If the DHCP server is running Windows Server 2016, these requests will be treated as if no SoH is present and will grant a normal DHCP lease.
  • If servers running Windows Server 2016 are RADIUS proxies that forward authentication requests to a Network Policy Server (NPS) that supports NAP, these NAP clients will be evaluated as non NAP-capable.

For more information, see Features Removed or Deprecated in Windows Server 2012 R2

Comments (0)

Skip to main content