Unusual AD Configuration Question Server 2008 R2


this request suggestions. have call unique situation , hoping advice. have handful of domain controllers part of same domain dns running. domain controllers separated extended period of time each other without possibility communication eventually, let's 240 days, come in contact each other. in light testing we've had issues each of domain controllers taking extremely long time restart (i imagine that due lack of dns) don't know happen in coming months.

question, suppose, how of this? create separate domains or federated domains? read-only dcs? in odd case each of dcs may have run dns well. recommendations appreciated!

dc's should not disconnected network or unavailable more forest tombstone lifetime setting (either 60 or 180 days). see these links:

http://technet.microsoft.com/en-us/library/cc784932(v=ws.10).aspx

http://support.microsoft.com/kb/216993

if this, need careful not delete objects on of dc's. see article lingering objects:

http://technet.microsoft.com/en-us/library/cc738018(ws.10).aspx


richard mueller - mvp directory services



Windows Server  >  Directory Services



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS