Windows Forum

Ask something
Discussion Locked

2 W2K servers on same network/domain

0 helpful
5 replies

by iiajason 1 view

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

I allready have 1 W2K server in test-mode on my network doing its thing. I now want to add another W2K server that will be the Live machine once testing is done, but both servers will remain on the network for some time. Will introducing anther Domain controller freak out my allready existing domain controller once AD is setup? I know w/ W2k, PDC's and BDC's are nolonger a thing, but should installing/putting it on the network not be an issue?
Please advise why it will not be an issue if thisis the case. THanks in advance.

5 replies

by duskos

Domain Controllers (DC's) are computers that authenticate users. The idea is that a user logs on once and has access to all resources (directories, files, printers etc) on all computers in the domain.

In Windows NT 4.0 there was a single master model. It means that one DC is a primary (master)or PDC. You do all the changes on this computer (create new users, delete users, change passwords). Other DC's were backup DC's or BDC's. They held replica of security database on a primary DC. BDC's were used to authenticate users, ie users could log on to the network by contacting BDC, but when they were changing password they did it on PDC.
Windows 2000 is a multimaster model. Computers running Active Directory services are DC's. However, they are (more or less) equal. It means that you can make changes on any DC on your domain and they will be replicated to all DC's. (It is slightly more complicated because domains can be organized in domain trees and forests). Anyway, not only that two DC's in one domain will get into each other's way, but it is actualy considered a must to have at least two DC's per domain (for security reasons). In secure places they recommend two DC's per site.

by umbral-echo

This will work perfectly and efficiently. I should make you aware of some of the hidden issues that will cause you problems later if you don't know about them.

The only forseeable problem you will have will occur when you try to take the first server offline when you no longer need it. Because it was the first to be installed, it has taken several roles that should be moved before doing away with it. It is also the only Global Catalog server for your network and this must be rectified beforeshutting the first server down.

1. Move the Operations Master Roles to the live machine. This requires you to move the five different operations masters roles using the Active Directory Utilities. Check the Windows Help on the Server machine and it will give a pretty good procedure for doing this.

2. Create another Global Catalog server. Open Active Directory Sites and Services. Expand the Default-First-Site-Name (or the site you have configured) icon and the folder labelled "Servers". Find the new server in the list and expand it. You will see an "NTDS Settings" icon. Left-click once on it to highlight it and then Right-Click on it and choose Properties. You will see a little check box labelled Global Catalog. Enable it.

Once youhave done these things your test machine can be decommisioned.

This discussion is closed to new replies.