Discussion Locked

Having another Win2K Server as Secondary

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, I've installed one Win2K Server & Active Dir Services on it. It authenticates users etc. fine (like a PDC on NT Domain). I need to have one more Win 2K as backup / Secondary for this. How do I go about it & exporting users/permissions etc.
I understand if I install Active Dir on the new one, it becomes primary. Do let me know ASAP.
Akash

9 replies

by erikdr

ADS doesn't know about PDC or BDC, it just has Domain Controllers. However there are some 'master' roles inside each domain, e.g. Global Catalog - this role is usually occupied by the first DC installed on the domain.

So you can simply install ADS on the second machine, and have it join the domain (and forest) of the first machine. Basically it will then act as backup controller...

Hope this helps,

- The Netherlands

by beermonster

Hi,
I'll go in to a bit more detail below, but the short answer is that you can build a server, use DCPROMO to make it another domain controller in your domain, and that will be job done. Unlike NT, Win2k uses a multi master model. This basically means that with a PDC, ALL changes were made on the PDC and then sent to any BDC's. However ANY win2k domain controller in an active directory environment can accept changes, and then 'swap' changes with the other win2k domain controllers on the domain. In order to support downstream clients (IE NT4 domain controllers etc), ONE win2k server (by default the first one you built) will hold the role of 'PDC Emulator'. This server will announce itself to downstream clients who believe they need to talk to a PDC, and service their requests as if it was a PDC. The result of you putting in another server will be that any authentication or updates will be serviced by either server, while any client that specifically looks for a PDC will be answered by your first server. Hopethis helps.

by lordinfidel

There is One more issue that was not addressed by the above 2.

Even though you install AD onto another 2K server. It will not authenticate requests until it is made a Global Catalog server.

This is done in the Sites and Services area/NTDS settings for that server.

As the second poster said....

Use DCPROMO to accomplish this. Join the server into an existing Forest/Existing Tree.

Once it is done, you will need to go to Sites and Services to check off the GC box in NTDS settings.

Also If this Server is one that you want to be the PDC Emulator (if you have NT BDC's still on your domain) then you can transfer that role to the new server.

As the other posters have stated, AD knows nothing about PDC's and BDC's with the exception of the PDC emulator.

by firestartah

Install win2k server onto your new machine. When setup, run dcpromo.exe and elect to add another domain controller to an existing domain. This server will then automatically replicate the AD from your existing DC.

This discussion is closed to new replies.