Win 2k Domain Controllers

  • Thread starter Thread starter Will
  • Start date Start date
W

Will

I have 2 Win2k domain controllers. They replicate alright
between each other (one way replication it seems) however
there is one thing that I would like to get working: I can
only do changes on the first domain controller (first
installed), the changes do replicate to the second domain
controller however if i am take the first domain
controller off the network then everything functions fine
however I can make no changes on the second domain
controller. It seems to me that the first domain
controller that I installed is acting like a PDC (Win NT
terms) and the second domain controller is acting like
BDC. I thought that in Win2k both domain controllers act
like PDC's so if one is off the network then changes can
be made on the second one as if nothing happened. How can
i promote the second domain controller to be a PDC like
the first one so in case first one fails I can still make
changes on the second. An answer would be greatly
appreciated.
 
I thought that in Win2k both domain controllers act
like PDC's so if one is off the network then changes can
Click to expand...


Not entirely.
When you remove the first Win 2k DC and want another DC to take ove you need
to account for the 5 FSMO roles, most likely the Global Catalog, and *maybe*
the DNS.

For the 5 FSMO roles see:
FSMO ROLES

Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain Controller

http://support.microsoft.com/default.aspx?scid=kb;en-us;255504

HOW TO: View and Transfer FSMO Roles in the Graphical User Interface

http://support.microsoft.com/default.aspx?scid=kb;en-us;255690

Flexible Single Master Operation Transfer and Seizure Process

http://support.microsoft.com/default.aspx?scid=kb;en-us;223787

FSMO Placement and Optimization on Windows 2000 Domain Controllers

http://support.microsoft.com/default.aspx?scid=kb;en-us;223346





For the Global catalog see:

How to: Create or Move a Global Catalog in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;313994





For DNS, if the only DNS server on the domain is the first DC, you need to
remember that without DNS AD ceases to function correctly. If the first
server is the only DNS server on the domain all clients *should* be pointed
to this server for DNS.

I would suggest setting up DNS as AD integrated. That way the second DC has
the correct DNS records. When you remove the first DC you have to point your
clients to the second DC for DNS.



hth

DDS W 2k MVP MCSE
 
Back
Top