Windows Server / DNS, DHCP & Server Networking
Find an exhausted Windows DHCP scope before expanding it
A client lease failure may be isolated to one subnet even though other scopes work. Inspect scope utilization and exclusions.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-DhcpServerv4ScopeStatistics -ComputerName DHCP01Read the result
With DHCP tools and authorized access, the statistics show lease use for configured IPv4 scopes. Available counts must be considered with exclusions and reservations.
Resolve and verify
Identify the affected scope and compare lease duration, stale clients and subnet design. Plan approved capacity or lease-policy changes and verify new clients obtain correct settings.
Before changing production
Do not expand a scope into addresses already used statically or outside the actual subnet.