Control LogonServer

[corey]

Our organization contains over 240 sites...logically
divided into 14 regions (affiliates).

We have implemented AD for the entire organization into 1
forest/1 domain.

We have strategically placed 2 DCs into each logical
region. 1 in their head office/site and 1 in their next
largest/secondary office/site.

Since we have all offices in each region in a single site
(so they logon to their head office), is it possible to
force logons to use their secondary office/site DC in the
event their main DC is overloaded (rather than randomly
pick a DC from another region)?

This is becoming an issue since these regions fund their
own resources and would not like to see other regions'
clients logging onto their DCs consistently...

In summary, is it possible to force clients use a
specified secondary dc/site in the event their site DC is
unavailable?

thanks,
Corey

 

[Jerold Schulman]

Our organization contains over 240 sites...logically
divided into 14 regions (affiliates).

We have implemented AD for the entire organization into 1
forest/1 domain.

We have strategically placed 2 DCs into each logical
region. 1 in their head office/site and 1 in their next
largest/secondary office/site.

Since we have all offices in each region in a single site
(so they logon to their head office), is it possible to
force logons to use their secondary office/site DC in the
event their main DC is overloaded (rather than randomly
pick a DC from another region)?

This is becoming an issue since these regions fund their
own resources and would not like to see other regions'
clients logging onto their DCs consistently...

In summary, is it possible to force clients use a
specified secondary dc/site in the event their site DC is
unavailable?

thanks,
Corey

See http://support.microsoft.com/default.aspx?scid=kb;en-us;247811,
How Domain Controllers Are Located in Windows

Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com