Question about RODCs

here situation: small company 8 locations across country.  setting active directory in our corporate headquarters first our first domain controller, , bringing our other locations domain afterwards.

our concern don't want our users in our remote locations unable login domain due failure of internet connectivity @ headquarters.  rodcs appropriate tool providing user authentication locally in our branch offices should have connectivity failure @ headquarters?  or rwdcs more appropriate?  matter of company policy, not want single points of failure.  if, whatever reason, primary rwdcs @ headquarters cannot reached branch office, should not prevent users in our branch offices logging domain.

users still able log workstations if connectivity corporate's domain controller lost.  accomplished using credentials cached on workstation.  users still have access local files.  need dc comes play if users try share files on network.  need dc handle 'secure handshakes' required sharing.  if have local file server, form of file sharing, access dc required that.

a rodc more secure rwdc.  think exchange requires rwdc if install remotely, otherwise, things work fine rodc.  there exceptions, have check want run remotely on dc before deploy rodc.

---

.:|:.:|:. tim

Windows Server  >  Windows Server 2012 General