Requirements to bring up temporarily network isolated DC

hi folks.

a question has been nagging me while..   school district on 50 physical sites (with matching ad sites , subnets).   each site has domain controller. (the primary data center has 3 dc's, including fmso role holder).

we have found if 1 of remote site loses it's network connectivity rest of wan, , domain controller reboots, fail restart ad (and therefore dns) because can't connect it's replication partners.  

in sandbox, found can ad , dns on isolated dc disconnecting dc's network card during boot up.

is expected behavior? or sign of misconfiguration somewhere?  are there work arounds can done pre-emptively?

thanks thoughts

hi paul j. landry:

thanks posting.

>>each site has 1 domain controller. have found if 1 of remote site loses network connectivity rest of wan, , domain controller reboots, fail restart ad (and therefore dns) because can't connect replication partners.  

yes, fail because cannot replicate partners. in scenario, recommend install rodc in remote site.  remote sites have poor network bandwidth when connected hub site , hamper access network resources. rodc  faster logon times , have more efficient access resources on network. more, allow credential caching on rodc.  when remote site loses connection,  dc replicate rodc.

                                                                                                                 

for more information rodcs, see read-only domain controller (rodc) planning , deployment guide (http://go.microsoft.com/fwlink/?linkid=135993).

>>in sandbox, found can ad , dns on isolated dc disconnecting dc's network card during boot up. expected behavior? or sign of misconfiguration somewhere?  are there work arounds can done pre-emptively?

if steps, dc becomes separate server.  we don’t recommend do.

best regards

mary dong

Windows Server  >  Directory Services