Delete instead of deactivate DHCP scope??

  • Thread starter Thread starter Inverted Prophecy
  • Start date Start date
I

Inverted Prophecy

Hello all,

I have a question regarding scope deactivation and deletion in DHCP.

We want to migrate a superscope with member scopes 10.0.128-130.x /24
to a 10.0.128.x /22 range (it's an HP switch issue). The problem is I
can't create the 10.0.128.x /22 scope, since 10.0.128.x is already in
use, which DHCP kindly points out when creating the scope.
Deactivating the superscope doesn't help. Deleting the superscope
does, but Microsoft explicitly recommends AGAINST doing this. What
could be the problem with deletion instead of the deactivation/
deletion combination and several client reboots/ ipconfigs? I'll take
the NAKs for granted if I have to.

Thanks for any pointers!

Casper.
 
Inverted Prophecy said:
We want to migrate a superscope with member scopes 10.0.128-130.x /24
to a 10.0.128.x /22 range (it's an HP switch issue).
Click to expand...

Migrate to where? What exactly are you doing?
 
Back
Top