Discussion Locked

Win2K domain controller

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I recently upgraded my NT 4.0 BDC to WIN2K server but elected not ot load AD, so it is just a member server. I still have a NT4.0 PDC. I now want to make the WIN2K server a BDC, but when I go through the process of loading AD (as an additional controller) it wants a Domian name, our domain name is NTSERVER, but it says it can't find it although it communicates fine on the network and can find and be found by any other computer on the network. Do I need to select the "domain controller for a newdomain" option during AD installation even though I want to continue using the current PDC as a PDC? Is it possible to use an NT 4.0 PDC with AD?

5 replies

by maxwell edison

Greetings,

The answer to your last question is no.

"Windows 2000 Active Directory" is the Windows 2000 name for a domain. Windows 2000 doesn't allow you to upgrade any of your backup domain controllers until you've upgraded the primary domain controller.

It's recommended that you use a new box with a fresh install of Win2000 as your PDC instead of upgrading existing NT 4.0 boxes.

Maxwell

by netuser

You should upgrade your PDC first as a new domain. After a successful upgrade, the domain controller appears as a W2K domain controller to W2k servers and clients but emulates a Win NT 4.0 PDC to other servers and clients. Next upgrade the BDC one at a time if you have more than one. When completed successfully, you have the option fo changing the domain from Mixed mode (where NT domain controllers can exist in the domain)or Native mode (where ONLY W2K domain controllers can exist in the domain)
Caution: you cannot revert to Mixed mode after changing to Native mode. In your case, you select Mixed mode.

This discussion is closed to new replies.