Hi,

I've got two servers running Windows 2003 and one of them is setup as a
domain controller, I would like to have the second set up as a
secondary domain controller, but am having difficulty in doing so. If
anyone could point me to a tutorial on how to set up a secondary domain
controller or any tips would be helpful.

Thanks in advance

Simon

In news:1155227349.417107.185460@i3g2000cwc.googlegro ups.com,
accyboy1981@gmail.com <accyboy1981@gmail.com> typed:

See
http://www.microsoft.com/technet/pro.../addomcon.mspx
and
http://technet2.microsoft.com/Window....mspx?mfr=true

Basically, you need to run dcpromo, install DNS (I would!) and make the
server a GC (global catalog server).

If this is going to be in a different location (e.g. you have another office
linked via leased line/VPN) you also need to set up another site/subnet in
AD Sites and Services. If, however, it's on the same LAN, no need to go
there.

What is the second server doing? It's usually a good idea to have a DC
do only "DC stuff". It's strongly discouraged if you are running
Terminal Services or Exchange...

It's a great idea to have multiple DCs. It's almost mandatory if you
want to have a decent chance of recovering from a server failure. You
might consider getting a good low end server instead (or even a decent
workstation) as your second DC.

You should first off make sure that DNS is integrated with AD on the
existing DC. If it isn't, you should do it.

Next, set up the new server.

Install DNS on it (don't worry about configuring DNS).

Run DCPROMO to convert it to a DC.

Wait a while to allow full synchronization with existing DC.

Set it as a Global Catalog (this will allow workstations to log on if
the other DC is down).

You could test things at this point. Try changing one workstation to use
only the new DC as the DNS server. See if it has any problems getting
to servers and/or web sites (You should probably run IPCONFIG /FLUCHDNS
on the workstation first). Next, take the first DC off line (easiest way
would to be to unplug the network cable) and try to log on to the domain.

Obviously, the above tests should be done off shift....

If everything looks OK, you should update the DNS settings on the new DC
to use itself as the primary DNS serve and the first DC as the
secondary. All other servers should point to the first DC as primary and
the new one as secondary. You will want to update the DNS settings of
your workstations to point to both DC's for DNS resolution.

Regards,
Hank Arnold

accyboy1981@gmail.com wrote: