If the Hub Transport role is not co - located, the service
uses a round - robin process to distribute the load. The Hub Transport server that is notified retrieves the
message and begins transport processing.
The next step is to determine the ultimate destination, which is the end - to - end route. After it is selected, the
route is not recalculated unless there are routing configuration changes. The route selection is calculated
from a set of routing tables that are generated when the Microsoft Exchange Transport service starts. The
information in the routing tables is logged. By default are they are located in C:\Program Files\
Microsoft\Exchange Server\TransportRoles\Logs\Routing .
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
Part III: Working with PowerShell in a Production Environment
302
Route selection uses an algorithm to match valid connectors against all connectors in the organization
except Routing Connectors, until a single path is left. If no paths are left after running through the process,
recipients are marked as unreachable or a non - delivery report (NDR) is generated. The algorithm is
based on the following:
Connector scope
Target address space
Connector restrictions
The path with the lowest cost from source to destination, with the preference to stay within the
Exchange Server 2007 routing group as long as possible
The path with the least number of hops
The first site alphanumerically sorted
The destination address is a combination of delivery type and domain.
Pages:
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437