domain
Why is it common practice to implement mor than one domain controller per domain
Software/Hardware used:
Software/Hardware used:
ASKED:
October 17, 2007 4:07 PM
UPDATED:
November 24, 2007 7:15 PM
Answer Wiki:
The very simple answer is to have at least 2 domain controllers in each domain, but i'd like to recommend take a look on the following link:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/dsbl_fsm_whrc.mspx?mfr=true
To see all answers submitted to the Answer Wiki: View Answer History.
The reason is for redundancy. This way, if a domain controller were unavailable for any reason — planned or unplanned, the domain will for all intents and purpose continue to function. Now there are some caveats that go along with this and they are that DNS must also be available. So the zone for the domain should be Active Directory-integrated and in a two domain controller scenario, both domain controllers should also be DNS servers.
Some operations will not be available to the domain if the domain controller holding the required flexible single master operations (FSMO) role is unavailable. For example, if the schema master, which by default is the first domain controller installed in a forest is not available when installing an application that extends the schema in anyway, then that will likely be a show stopper for installing that application until the domain controller holding the schema master role is brought back online, or the role is seized by another domain controller.
In total, there are five FSMO roles and they are:
1. Schema Master
2. Infrastructure Master
3. PDC Emulator
4. Domain Renaming Master
5. RID Pool Master
For more information on domain controllers and FSMO roles, review the following URL http://www.petri.co.il/understanding_fsmo_roles_in_ad.htm.