Promote Server to Domain Controller

  • Thread starter Thread starter r0adh0g
  • Start date Start date
R

r0adh0g

I have a Windows NT 4.0 Domain controller and a Windows 2000 Member Server.
How can I promote the Windows 2000 Server to become the domain controller
and inherit
all of the user, security information, DHCP, DNS, Etc. from the Windows NT
4.0 Domain
Controller and then deactivate the Windows 4.0 Domain Controller?

Any advice would greatly be appreciated. I also apologize for cross
posting, but I did
not know which group would be most relevant.

Thanks,

rh
 
This would be what is called a migration to Windows2000 Active Directory.
This is NOT something to take lightly and I would suggest some serious
reading on Active Directory. There are major changes between a NT4 domain
and Windows2000 Active Directory Domain and you need to do some research
before attempting this so that you don't shoot yourself in the foot. Windows
2000 machines cannot be domain controllers in a NT4 domain, the whole domain
needs to be upgraded to a WIndows2000 Active Directory domain. This would be
a good place to start

http://www.microsoft.com/windowsserver2003/technologies/directory/activedirectory/default.mspx
 
r0adh0g said:
I have a Windows NT 4.0 Domain controller and a Windows 2000 Member Server.
How can I promote the Windows 2000 Server to become the domain controller
and inherit
all of the user, security information, DHCP, DNS, Etc. from the Windows NT
4.0 Domain
Controller and then deactivate the Windows 4.0 Domain Controller?

Any advice would greatly be appreciated. I also apologize for cross
posting, but I did
not know which group would be most relevant.

Thanks,

rh
Click to expand...

Heed Scott's comments. Upgrading from NT4 to W2K AD is 80%
plannification/testing. You would well be advised to test/document the
procedure first. Installing a temporary NT4PDC outside the network and
upgrading it to a W2K AD rootDC is highly recommended.

The only viable and safe way to upgrade the network is to:
1. Take an NT4 BDC offline for recovery purposes.
2. The only NT4 server that can be upgraded is the PDC, attempting to
upgrade any other NT4 server is suicide.
3. Run winnt32 /checkupgradeonly to verify both software and hardware
compatibility. I'ld also add that a bios upgrade should be considered.
4. Upgarding from an NT4 to a W2K domain means you are migrating from a flat
netbios domain model to a dns hierarchical architecture. This, in itself, is
a subject that can be discussed 'ad nauseum' but i doubt that this e-mail
can carry even the basics on the subject of dns hierarchy. Suffice it to say
that W2K means you HAVE to know dns intimately.
5. A domain using a name scheme like domain.local can only have it's name
changed/modified if either the domain is destroyed or if you upgrade to
W2K3. hence the need to plan.
6. While you are probably thinking, "hmm, this sounds like a daunting task":
my response is that its well worth the effort when executed as designed.
 
Back
Top