Upgrade static lan to DHCP

[Alister]

We have a well established LAN which is 2k server based, but is
currently static addressed.
We have finally got the go-ahead to put a dhcp server on the LAN.
Currently, we have a Primary DC running Active Directory and DNS, a
Secondary DC running Active Directory,
DNS and WINS, and a third Server which is not a DC which is running
Exchange server 2K.
We also have a file server, and a development server running
Microsoft SQL Server.
All clients are either 2k SP4 or XP SP2.

Questions:
Are there any gotcha's we should be aware of when implementing this
change?
Does it matter which DC we put the DHCP service on?
Is it correct we still need WINS for Exchange to run properly?

Any comments would be gratefully received.

Alister.

 

[Kurt]

We have a well established LAN which is 2k server based, but is
currently static addressed.
We have finally got the go-ahead to put a dhcp server on the LAN.
Currently, we have a Primary DC running Active Directory and DNS, a
Secondary DC running Active Directory,
DNS and WINS, and a third Server which is not a DC which is running
Exchange server 2K.
We also have a file server, and a development server running
Microsoft SQL Server.
All clients are either 2k SP4 or XP SP2.

Questions:
Are there any gotcha's we should be aware of when implementing this
change?
Does it matter which DC we put the DHCP service on?
Is it correct we still need WINS for Exchange to run properly?

Any comments would be gratefully received.

Alister.

There are no "gotchas" as far as DHCP goes as long a it's configured
correctly and just a smidge of planning is involved. DHCP (unless you're
talking about a huge number of clients) is very low overhead, so it
shouldn't matter which server it goes on. I'd say off-hand, just put it
on the one with the least load. As far as planning goes, you can either
set up your scope to be different than what your static scope is now, or
just configure all the computers for DHCP and shut them down before you
start the service then bring them back up afterward. Everybody has their
own way of doing things, I usually leave the lowest numbers out of the
scope for statically assigned things like routers, printers, etc. (1 -
19 or so), and the highest numbers for servers (230 - 254?).

....kurt

 

[Alister]

Alister wrote:

There are no "gotchas" as far as DHCP goes as long a it's configured
correctly and just a smidge of planning is involved. DHCP (unless you're
talking about a huge number of clients) is very low overhead, so it
shouldn't matter which server it goes on. I'd say off-hand, just put it
on the one with the least load. As far as planning goes, you can either
set up your scope to be different than what your static scope is now, or
just configure all the computers for DHCP and shut them down before you
start the service then bring them back up afterward. Everybody has their
own way of doing things, I usually leave the lowest numbers out of the
scope for statically assigned things like routers, printers, etc. (1 -
19 or so), and the highest numbers for servers (230 - 254?).

Thanks very much for your response, Kurt, we just wondered if
Exchange
or SQL server might have a hiccup when we changed the addressing,
particularly as we had decided (as you suggest) to move the servers
Ip's to the higher numbers of the range.

Thanks again,

Alister.