Multiple W2K Domain controllers

[Guest]

I thought I knew how to do this, but I am stumped. I am helping a non-profit
with their five W2K Servers and a single NT 4.0 PDC Server. I want to
upgrade the NT PDC to W2K Server but I am haven't yet found a W2K complient
driver for the DPT RAID. When I upgrade it to W2K Server as a DC, I need
users to be able to login to the single domain if this main server is down.
If I am not using active directory (and this may be what is confusing me) how
do I set up the W2K DCs so they share login information so if one of them is
down, the others will handle the logins?

Thanks

 

[Glenn L]

Let me make sure I am clear.
You have an NT4 domain with a single DC (the PDC) and 5 W2K member servers.
You are having a challenge finding W2K SCSI storage drivers for your PDC so
you can upgrade it to W2K and make it a W2K DC for the domain.

Lets assume the NT4 box will not reliable upgrade to W2K.
You will need to bring another computer onto this network to RUN NT4 server
as a BDC in the domain. This will be temporary and can easily be a
glorified PC (that can run W2K server of course).
Once it is a BDC, you promote it to PDC. This demotes the original PDC to
BDC.
You then upgrade this PDC to W2K and make it a DC in your domain (active
directory)
You now have a W2K DC (acting as PDC emulator....) and a NT4 BDC.....
You will now need to promote one of the 5 member servers to a domain
controller.
Once you do this, you can then demote the PC and turn it off.
now you have two DCs. A W2K DC and a NT4 BDC.

If the NT4 box is down, the W2K DC will continue to authenticate users.


--
Glenn L
CCNA, MCSE 2000/2003 + Security

"Confused W2K Server user" <Confused W2K Server
(e-mail address removed)> wrote in message
news:[email protected]...

 

[lforbes]

I thought I knew how to do this, but I am stumped. I am
helping a non-profit
with their five W2K Servers and a single NT 4.0 PDC Server. I
want to
upgrade the NT PDC to W2K Server but I am haven't yet found a
W2K complient
driver for the DPT RAID. When I upgrade it to W2K Server as a
DC, I need
users to be able to login to the single domain if this main
server is down.
If I am not using active directory (and this may be what is
confusing me) how
do I set up the W2K DCs so they share login information so if
one of them is
down, the others will handle the logins?

Thanks

Hi,

As your PDC is still NT 4.0, you are still running an NT 4.0 Domain.
The 5 Windows 2000 Servers are simply "Member Servers" and currently
have no role in authentication etc.

There are two ways to upgrade your NT 4.0 Domain to Windows 2000.

1> If you stick your Windows 2000 Server CD into the NT 4.0 PDC and
install it will AUTOMATICALLY install Active Directory and DNS
therefore converting your current NT 4.0 Domain into a Windows 2000
one. You will have no choice about the Domain Name etc. as it will
just use whatever you have now. Make SURE your DNS name is Simply
your Domain Name with a .local extension. Eg. mydomain (NT)
mydomain.local (W2K)

If you do it this way, you can simply run DCPromo on one or more of
your Current Windows 2000 Servers and make them DC’s in the W2K
Domain. In Windows 2000 ALL DC’s are equal (unlike NT) so if one goes
down, the other can do the job. However, there are 5 roles you must be
aware of. These roles reside on the FIRST DC installed (which would be
your previous NT DC). I recommend transfering these roles to a Newer
server using Active Directory. Once everything is replicated and the
roles are transfered and all files/shares are transfered, I recommend
removing the previous NT machine from the Domain (Using DCPromo again)
reformating it and installing Windows 2000 cleanly to avoid any
problems and then make a DC with DCPromo. I have found keeping the
"upgraded" NT is not the best idea as it still keeps all the old
registery junk and old paths eg. Profiles in the Windows directory
etc.

2> The second way would be to remove one of the Windows 2000 Servers
from the NT Domain and make it a NEW Windows 2000 Domain using
DCPromo. You can then chose your own Domain name and DNS Name if you
want to change it. You can then use the Active Directory Migration
Tool available from MS to transfer all your users, computers etc. This
would be more work, but would be cleaner.

Cheers,

Lara