if you are using super scope this won't work, you must not use it super scope in server 2022
try deleting superscope it won't delete the child scope it will work
--If the reply is helpful, please Up vote and Accept it as an answer–
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Version 10.0.20348 Build 20348
I have installed 2 DHCP server with failover, I have a scope with 4045 client IP-address an a lease time with 9 hours.
Now server says there is no IP-address available , but scope statistics say there should be 21% available.
If I check with Get-DhcpServerv4Lease on scope I can se all 4045 IP-address are in use. And more then 3700 IP-address where lease time has expired.
Why does DHCP server not release IP-address, after lease timeout. If we don't fix this, we need to roll back to 2016 server!!!!
if you are using super scope this won't work, you must not use it super scope in server 2022
try deleting superscope it won't delete the child scope it will work
--If the reply is helpful, please Up vote and Accept it as an answer–
Hi there,
This issue might occur because DHCP servers lease the IP addresses that are actually owned by some client after the migration. Then, these IP addresses are marked as BAD_ADDRESS. Check if you have updated the Server 2022 with all updates.
If the lease period expires and the DHCP client has not yet renewed its IP configuration data, then the DHCP client loses the IP configuration data and begins the DHCP lease generation process again
Below threads discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.
IPs are not released after the lease expires https://social.technet.microsoft.com/Forums/windowsserver/en-US/87f5fdef-1e6e-4b5f-8617-efcd471d0e9e/ips-are-not-released-after-lease-expire?forum=winserverNIS
--If the reply is helpful, please Upvote and Accept it as an answer–