When you adjourn I Windows client operating system to a domain and then restarted the client complete
at the main controller location and registration process.
The goal of this registration process is to locate the Domain Controller with the most efficient and
closest location to the client's location based on IP subnet information.
The process for locating a domain controller is as follows the new client queries for all domain controllers
in the domain as the new domain client restarts.
It receives an IP address from a DCP server and is ready to authenticate to the domain.
However the client does not know where to find or domain controller.
Therefore the client queries for a domain controller by wearing the underscored DCP folder which contains
the as several real records for all domain controllers in the domain.
The second step is that the client attempts and Eldad been to all domain controllers in a sequence.
Janus returns a list of almost matching domain controllers and the client attempts to contact all of
the domain controllers on its first startup.
The third step is that the first domain controller response the first domain controller that responds
to the client examines the client's IP address growth references that IP with subnet objects and informs
the client of the site to reach the client belongs.
The client stores the site name in its registry and then whereas the domain controller in the site's
specific DCP folder.
The next step the client queries for all domain controllers in the site.
Dennis returns a list of all domain controllers on the site.
Step number five.
The client attempts an old Debian sequential ID to all domain controllers in the site.
The domain controller that responds first authenticate the client and the last step.
The client forms an affinity the client forms an affinity with the domain controller that responded
first and then attempts to authenticate with the same domain controller in the future.
If the domain controller is unavailable the client.
Whereas the sites disappear folder again and again attempts to bind with the first domain controller.
That response in the site if the client moves to another site which might be the case with a mobile
computer the client attempts to authenticate to his preferred domain controller the Domain Controller
notices that the client's IP addresses associated with a different side and it then refers the client
to the new site.
The client then whereas DNS for domain controllers in the local side you can configure a site to direct
users to local Corpus of replicated resources such as shared folders replicated within a DFS namespace.
There might be scenarios in which you require only service localization with no need for a domain controller
located within the site.
In this case a nearby domain controller will register it is a a record in the site by using the site
coverage process aside without a domain controller generally is covered by a domain controller in a
site with the lowest site Lynn cost to the site that requires coverage.
You also can configure site coverage and a record priority manually.
If you want to control authentication in sites without domain controllers.