Discussion Locked

Windows 2000 upgrade, WINS and DHCP

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am currently planning the migration of our company's network from NT 4.0 to Windows 2000. We currently have 1 PDC and 1 BDC. We have purchased two powerful Dell servers to serve as new domain controllers. I am currently installing NT 4.0 on both of them and establishing them as additional BDCs on the network. I then plan to promote one of the new Dells to PDC and then begin the upgrade to Win2K.

Once this server is upgraded, WINS and DHCP will still reside on the server that once served as the NT 4.0 PDC (it was since demoted to BDC). My questions are these: Will these services still function normally on this NT 4.0 BDC? Do I need to include these services in my upgrade path on the PDC I upgrade to Win2K?

Your answers and comments are greatly appreciated!

Kelvin Tamayo
MCSE NT 4.0 & Windows 2000
Network Administrator
Life Extension Foundation

5 replies

by bchesmer

If you are moving to AD, I are pretty sure you should move your DCHP & WINS to the new server (W2K PDC).

Do you plan on leaveing the NT 4.0 around after the migration? If not, I would move this to one of the new W2k servers.

by timwalsh

While it is not an absolute requirement (DHCP and WINS will continue to function properly in a Win2K domain - just make sure you update your DHCP options to take into account any changes made during your migration), there are some added benefits to moving at least DHCP to a Win2K DC. DHCP, as implemented in Win2K, has the capability of dunamically updating your DNS table with address assigned through DHCP. NT4 DHCP does not have this capability. WINS, as implemented in Win2K, adds new recordtypes that take into account new roles and services added by Active Directory.

If such capabilities aren't important to your operations, then it is basically your call as to which way to go. If you plan on updating all your NT4 BDCs to Win2K DCseventually anyway, the upgrading of services can wait until you do so.

One other point in case you hadn't thought of it: if possible, take one of your NT4 BDCs completely offline before beginning your upgrade. This will provide you a fallback in case something goes horribly wrong with the upgrade (these are after all Microsoft products, and as we all know, bad things happen). If anything does go wrong, it could also affect any connected NT4 BDCs. If this does happen, you could take your offline BDC, quickly promote it to PDC, and at least have your domain up and running again in a short time (while you sort out the rest of the mess).

Good luck.

This discussion is closed to new replies.