Once the route is selected, the server
must decide which queue and connector to submit the message to. It is possible to alter the route with
Hub sites. It is important to understand that if a Hub site is along a least cost path, all messages must
route through it. This enables specific scenarios, such as a firewall preventing end - to - end network connectivity.
Next, this chapter showed how Exchange Server 2007 performs its backoff process when the
destination server is unavailable. This is also where the message retry settings where explained.
Another new concept to Exchange Server 2007 is delayed fan - out. To help conserve network bandwidth,
Exchange tries to split the message destined for multiple recipients as close as possible to the
remote sites.
An examination of troubleshooting showed common errors, the new Routing Log Viewer, and how
to configure and use message tracking. All of these methods are valuable to an administrator trying to
understand what happened to a message when a customer wants verification that a message
was delivered.
The next section showed the detail on how to configure link costs and Hub sites. It addressed the
common design in Exchange 2003 of the dedicated Exchange Active Directory site. Finally, the chapter
looked at the intricacies of coexistence with legacy Exchange implementations.
Pages:
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463