Creating a dedicated site for Exchange was done mainly to keep domain controllers
from being used by other services and applications. Because Exchange Server 2007 maps routing
directly to Active Directory sites, this practice no longer is recommended in most circumstances.
One way to mitigate the impact of competing resources is to upgrade domain controllers to the 64 - bit
Windows platform. According to the Exchange team ??™ s guidance, a 32 - bit domain controller can co - exist
with other applications and support up to 10,000 Exchange users. The 64 - bit platform increases this to
20,000 Exchange users, effectively double the load.
It is possible to create an effect similar to a dedicated site by using DNS to alter record priority and
weights. The TechNet article ??? Creating an Active Directory Site for Exchange Server ??? found at
microsoft.com/technet/itsolutions/msit/operations/adforexchangenote.mspx details
the steps for this design in the section on ??? How to Isolate Client Authentication Traffic from Exchange
Facing Domain Controllers. ???
It is also still possible to specify a static set of domain controllers for each Exchange server, but this is not
recommended. This solution requires a lot of manual work to maintain and can easily lead to problems.
Site Links
Site link costs help Active Directory determine the least cost route for replication and domain controller site
coverage.
Pages:
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453