Re: DHCP Issue in Windows Server 2008 R2 - Service restart problem

"Ckuderna" <(E-Mail Removed)> wrote in message
news:eecacd6d-e372-45dc-a02a-(E-Mail Removed)...
> Hi,
>
> has anybody run into this issue?
>
> I have a Windows Server 2008 R2 running as a DHCP server. It's the
> only role installed on the machine.
> I have about 10 scopes (IPv4) grouped into 2 super scopes.
> Now I want to remove the superscopes, which works fine.
> A while later I restarted the DHCP service and now the superscopes are
> back.
> Other settings, like options (scope and server) are not affected.
>
> I found some reports of this behavior in older Windows versions, but
> the systems were clustered or reconfigured in some special way. My
> implementation is straight out-of-the box, no special configuration.
>
> Is this a bug or how do I correctly remove the superscopes?


Interesting. What KB article did you read about the older version doing the
same?

Curious, have you tried deleting both superscopes, then creating a new scope
that falls in line with one of the superscopes, then restart the service?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

"Ckuderna" <(E-Mail Removed)> wrote in message
news:0cf600ba-2e6d-4f1f-82ac-(E-Mail Removed)...
> On 19 Okt., 15:30, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
> wrote:
>> "Ckuderna" <ckude...@googlemail.com> wrote in message
>>
>> news:eecacd6d-e372-45dc-a02a-(E-Mail Removed)...
>>
>>
>>
>> > Hi,
>>
>> > has anybody run into this issue?
>>
>> > I have a Windows Server 2008 R2 running as a DHCP server. It's the
>> > only role installed on the machine.
>> > I have about 10 scopes (IPv4) grouped into 2 super scopes.
>> > Now I want to remove the superscopes, which works fine.
>> > A while later I restarted the DHCP service and now the superscopes are
>> > back.
>> > Other settings, like options (scope and server) are not affected.
>>
>> > I found some reports of this behavior in older Windows versions, but
>> > the systems were clustered or reconfigured in some special way. My
>> > implementation is straight out-of-the box, no special configuration.
>>
>> > Is this a bug or how do I correctly remove the superscopes?
>>
>> Interesting. What KB article did you read about the older version doing
>> the
>> same?
>>
>> Curious, have you tried deleting both superscopes, then creating a new
>> scope
>> that falls in line with one of the superscopes, then restart the service?
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit
>> among
>> responding engineers, and to help others benefit from your resolution.
>>
>> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
>> 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>>
>> For urgent issues, please contact Microsoft PSS directly. Please
>> checkhttp://support.microsoft.comfor regional support phone numbers.
>
> Hi Ace,
>
> it was not a KB article it was some discussion on experts-exchange.com
> I believe.
>
> I was able to resolve this, but only via the command-line.
> If you delete a superscope in the GUI and then do a NETSH DHCP SERVER
> DUMP the superscopes are still there, as if you had never deleted
> them.
> Once you do a NETSH DHCP SERVER DELETE SUPERSCOPE <Name> it's finally
> gone and the GUI also shows that correctly.
> A little weird, looks like a GUI bug to me.
>
> I could not yet try what you suggested...
>
> Chris


Glad you figured it out. Expert-exchange can be helpful with many things. I
haven't had this problem with superscopes, so I can't really comment if it
is a GUI issue or something else going on. But good to hear you were able to
delete the superscope using netsh.

Cheers!

Ace