C
cst112
I am running a windows 2000 network with several locations and 2 domain
controllers per site.
My main site I have a domain controller I want to shut down for a while to
fix a raid problem. I have another domain controller in which I have
transferred all the FSMO roles to and I have also transferred the dhcp
service. The problem I notice when I shut down the one domain controller
during workhours is that it seems to affect client computers. Things like
Exchange email or DFS have problems. Shouldn't having another domain
controller keep the network up without giving the clients grief? The server
that I am shutting down has no other services besides being a domain
controller (it was the first server in the domain).
I am just curious of how this works so I know when I can shut down domain
controllers and when I can't for maintenance.
Thanks.
Kevin
controllers per site.
My main site I have a domain controller I want to shut down for a while to
fix a raid problem. I have another domain controller in which I have
transferred all the FSMO roles to and I have also transferred the dhcp
service. The problem I notice when I shut down the one domain controller
during workhours is that it seems to affect client computers. Things like
Exchange email or DFS have problems. Shouldn't having another domain
controller keep the network up without giving the clients grief? The server
that I am shutting down has no other services besides being a domain
controller (it was the first server in the domain).
I am just curious of how this works so I know when I can shut down domain
controllers and when I can't for maintenance.
Thanks.
Kevin