Clients selecting DC to login, etc

[Carlos]

Hello!

Hope all is well!

One site only has one DC, which, if it's ever down,
clients will have to traverse to another site in order for
them to login.

Planning on adding another DC in a site with only one DC
for backup purposes, in case the need ever arises.

System I wil be promoting to DC it's already loaded with
services & functions. Therefore, if adding second DC, what
will dictate to clients which DC to use?

Will they continue using the very first DC in site?

If not, is it possible to have them only use the original
DC, & only to use the backup DC when it's necessary? For
that last question, I think happens automatically U it
might the default way of behaviour.

Wouldn't like the new DC to be hit with logins, etc that
much unless strictly "necessary."

Thanks for the info & sorry for long explanation.

Carlos

 

[David Brandt [MSFT]]

Clients will generally sort of cache the dc that did their last validation
and try to go back to that one initially before trying others. Validation
etc is also based on their site info as they will try to validate/use a dc
in their own site, based on ip header info, before going to other dcs in
other sites for what they need. With what you have there, it sounds like
the clients will still try to go the the first one in that site and change
over to the new one if it's busy/not available/etc, and if neither do what
it wants, then go to another in some other site.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.