Moving DHCP and WINS

[prace]

I have three AD domain controllers. I want to retire one
of them in the near future, It is a DHCP server so I plan
to move it's scopes to another server
using dhcpexim.exe or by saving the registry key and
restoring to the other server (the new target server
doesn't currently service any scopes. Is one mehtod
preferable over the other?

I would like to also do a fresh install of one of the
other servers as it was upgraded from Windows NT 4.0. This
server is an active DHCP and WINS server. What is the best
way to preserve and transfer the configurations to the
newly installed server? Save the registry keys and restore
them as if I was moving them to another server?

Remove spam. after @ to e-mail.
Thanks.

 

[Phillip Windell]

I have three AD domain controllers. I want to retire one
of them in the near future, It is a DHCP server so I plan
to move it's scopes to another server
using dhcpexim.exe or by saving the registry key and
restoring to the other server (the new target server
doesn't currently service any scopes. Is one mehtod
preferable over the other?

Config the new DHCP with identical settings. Use Exclusions on both so that
each gives out 1/2 of the addresses. When you are confident that it is
working right, disable the DHCP on the old one and delete the Exclusions o
the new one so it can give out all the addresses.

On WINS, don't worry about it. Just get it running and point all the clients
at it.

 

[Parker Race]

-----Original Message-----
"(e-mail address removed)"

in message news:[email protected]...

Config the new DHCP with identical settings. Use Exclusions on both so that
each gives out 1/2 of the addresses. When you are confident that it is
working right, disable the DHCP on the old one and delete the Exclusions o
the new one so it can give out all the addresses.

Interesting idea, the only problem I see is we have a lot
of DHCP reservations that would need to be typed in.

On WINS, don't worry about it. Just get it running and point all the clients
at it.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


.

 

[Phillip Windell]

Interesting idea, the only problem I see is we have a lot
of DHCP reservations that would need to be typed in.

Yes, that is why you should avoid having a lot of Reservations. It is
sometimes better to use Exclusions, then statically assign the machines,
then if you replace the DHCP you only have to put the one Exclusion in
there. I think thier might be a tool for migrating that stuff but I don't
know of it personally. Hang around I'm sure someone else around here may be
able to help with that.

 

[Richard G. Harper]

Definitely use the DHCP Export/Import tool to make the move in the first
case. I have used it several times, once to migrate from an NT4 to a Win2K
server, then again to migrate to a newer Win2K server when the first one
started to become ailing. No problems with either move, though there was
some rebooting and release/renew work to be done at the end of the move.

As for the second case you might use the DHCP Export/Import tool to save the
settings, clean-install the server, then re-import the settings back onto
it. If you could do so with minimal network disruption then that would be
the easiest way. Don't know about WINS, I don't run any on my network so I
can't say what the best bet would be to re-create it on the new server.