Would you recommend placing various applications (i.e., Exchange, Access, user data or any other processor-intensive application) on an NT4 PDC (primary domain controller)?
The reason I ask is because I have never done that due to issues with the PDC failing and the BDC (backup domain controller) taking over, causing the complete loss of other system functions as noted above.
I completely built a domain with the PDC, two BDCs and two name servers. No other data or applications were allowed on those servers so they could do the job they were built for.
The decision of whether to consolidate services and applications onto a single server is entirely dependent on the resource load placed on those servers by your user base. I have had situations similar to the one you described, in which the PDC was the PDC and that was its only reason for existing. I've also had entirely satisfactory results running file sharing and network applications on domain controllers with sufficient hardware resources (RAM, processor speed, etc.) to handle the additional load. You are correct, however, in noting that a PDC-to-BDC failover will not do anything to fail over any applications that may be residing on the PDC. To accomplish this, you will need to implement some form of hardware or software clustering solution, either the Microsoft Cluster Service or a third-party solution.
Dig deeper on Enterprise Infrastructure Management
Related Q&A from Laura E. Hunter
Active Directory expert Laura E. Hunter offers some advice for changing the IP addresses of domain controllers.continue reading
A Windows administrator moving from Windows Server 2003 to Windows Server 2003 R2 wants to perform a restore of a previous server to a new one ...continue reading
An admin has two domains and two Active Directories. He wants to know how to join the Active Directories so that internal staff can access both, but ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.