What you need to know
Which Windows Server role supplies DHCP relay, and what must exist on the server side?
Potentially affected
Administrators deploying a Windows Server DHCP relay agent between subnets.
DSE recommendation
Prepare a diagram linking one client subnet to its relay and intended DHCP scope.
Source facts
A DHCP relay forwards client broadcasts toward a DHCP server on another subnet, allowing that server to supply addresses and configuration. Microsoft’s prerequisites include a Windows Server computer in the remote subnet and a DHCP server with a scope for that subnet. The relay belongs to the Remote Access role. Installing the DHCP Server role does not install this relay feature. Microsoft documentation.
Applicability
Identify the client subnet, relay interfaces, destination DHCP servers, and scope configuration. Review any existing relay devices and the intended network path before adding another forwarding point.
DSE recommendation
Prepare a diagram linking one client subnet to its relay and intended DHCP scope. Have the routing and address-management owners approve the interface and destination choices. Record the role installation and Routing and Remote Access configuration separately so another administrator can reproduce the intended forwarding path.
Verification
Use a controlled client lease request on the remote subnet and inspect the resulting address and options. Correlate client, relay, and server observations for that request. Repeat for each configured subnet and preserve timeouts or an unexpected scope assignment as failures requiring investigation before broader use.
Official references
Microsoft Learn: Install DHCP relay agent for Windows Server. Source reviewed September 8, 2026.
Review the official source
Install DHCP relay agent for Windows Server · Verified September 8, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE