ee99ee,
WIN2000 and WINXP clients will first authenticate against the DC with the
lowest weight. So, if you configure one DC to have a weight of 0 and
another to have a weight of 10 ( or 1 for that matter - anything higher than
0 ) then all of your clients will authenticate against the DC with the
weight of 0. The exception would be if the DC with the weight of 0 is not
available or the client does not receive a response ( not the same - but
usually the same - as the first reason ) within a set amount of time.
Now, the priority is used to create the 'balance' or 'ratio' between Domain
Controllers that have the same weight. So, if you have two Domain
Controllers that have a weight of 0 and a priority of 100 ( the default
setting ) then you have essentially a round robin effect going on. However,
if you had a really old server ( hardware wise ) and a really new server (
hardware wise ) and you wanted the new server to authenticate 4x as many
requests as the old server then you would set the priority to 80 on the new
server and to 20 on the old server, for example.
HTH,
Cary
ee99ee said:
Thanks for the information. So if I understand this right, setting the
priority for the _ldap SRV records for the site in which I want this
to effect will allow me to do what I want to do.
One question before I do this. What is the difference between the
Priority feild and the Weight feild? Currently, both have a Priority
of 0 and a Weight of 100. I assume I would need to change the first DC
I want people to use to 10 and the other one to 20 or something...
much like MX records... but what about Weight?
-ee99ee
"Tim Hines [MSFT]" <
[email protected]> wrote in message
You can use ldapsrvpriority . Take a look at 306602 How to Optimize the
Location of a Domain Controller or Global Catalog
http://support.microsoft.com/?id=306602 . See the section on "To Configure
a Domain Controller to Register SRV Records with Particular Priority"
--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
I have a slow domain controller from hell and a nice fast one. I have
the slow one so my network doesn't fall apart at the seams when the
fast one is down for a reboot or something. Is there a way to have
clients use the fast domain controller unless they can't connect to
it, at which point they can try the slow one? I just don't want to
have to use the slow one unless absolutly necessary...
-ee99ee
