AD Sites and Services - DC Locator Process

hi all. trying handle on dc locator process.

in environment there multiple sites. in ad sites , services 'site links' configured follows:

1) us

2) asia

3) europe

4) global

site link bridge contains 1-3 on list above.

site cost 1-3 set 102. link 4 set 100.

domain = me.domain.com

within domain there multiple sites, each configured subnet. typically many of sites contain single domain controller.

so domain wide there 'xx' dc's, site specific single dc.

my understanding site link the lowest cost used. in our configuration #4 global has cost of 100.

global contains 4 sites: 1 us, 1 asia, three from europe

question:

when dc in local site unavailable how client request handled?

my thoughts any dc within sites listed in site link global (us, asia or 1 of 3 european sites) service request. potentially dc in japan might used service requests client in uk if dc in local site becomes unavailable.

is understanding correct?

kind regards,

phil.

hi phil,

>>question:

when dc in local site unavailable how client request handled?

my thoughts any dc within sites listed in site link global (us, asia or 1 of 3 european sites) service request. potentially dc in japan might used service requests client in uk if dc in local site becomes unavailable.

by default, when client requests domain controller, dc locator process locates domain controller in site of client. if no domain controller available in site, dc locator returns domain controller in domain. if domain controller located in branch site instead of hub site, communication domain controller might slow. try next closest site group policy setting in default domain policy can improve location of domain controllers clients running windows server 2008 or windows vista.

the try next closest site group policy setting uses site link cost values determine next closest site site of client. try next closest site can affect how configure site link costs because affects order in domain controllers located. enterprises have many hub sites , branch offices, can reduce active directory traffic on network ensuring clients fail on next closest hub site when cannot find domain controller in closest hub site. more information, see enabling clients locate next closest domain controller.

ref:https://technet.microsoft.com/en-us/library/cc794885(v=ws.10).aspx

________________________________________
best regards,
cartman
please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com.

Windows Server  >  IPAM, DHCP, DNS