zoeythecat
Technical User
Hi All,
We have 3 domain controllers in a single Windows2003 domain. Our main domain controller(DNS,DHCP,WINS,GC) has been crashing because of a disk controller error. We plan on replacing this domain controller this coming Monday. The other 2 Domain Controllers are low end processors and not robust enough to handle active directory traffic if we transferred all the roles, etc. I have a few questions I was hoping someone could offer some insight on:
(1)It appears that when this server goes down, no one can connect, because all the FSMO roles, dns and dhcp and all the clients and servers are pointed to this server. What can I do to provide a failover, so when this server goes down, users would still be able to connect?
(2) What should be my best strategy replacing this server? I assume I promote a server to be a domain controller, transfer all the FSMO roles, make this a GC, transfer the DHCP database.
Any tips or suggestions would be greatly appreciated.
Thanks in advance
We have 3 domain controllers in a single Windows2003 domain. Our main domain controller(DNS,DHCP,WINS,GC) has been crashing because of a disk controller error. We plan on replacing this domain controller this coming Monday. The other 2 Domain Controllers are low end processors and not robust enough to handle active directory traffic if we transferred all the roles, etc. I have a few questions I was hoping someone could offer some insight on:
(1)It appears that when this server goes down, no one can connect, because all the FSMO roles, dns and dhcp and all the clients and servers are pointed to this server. What can I do to provide a failover, so when this server goes down, users would still be able to connect?
(2) What should be my best strategy replacing this server? I assume I promote a server to be a domain controller, transfer all the FSMO roles, make this a GC, transfer the DHCP database.
Any tips or suggestions would be greatly appreciated.
Thanks in advance