Figure 9-20
Notice that this points to CN=Trainee5,OU=ADUsers,DC=ExchangeExchange,DC=local as shown in
Figure 9 - 21 .
Failures to deliver to a Recipient could result if the user ??™ s primary SMTP address, for example, is
modified and EdgeSync did not synchronize the change to ADAM for some reason. Ensure that the
EdgeSync service is running and use the VerifyRecipient parameter to test that the user is
synchronized.
Part II: Working with Server Roles
262
For message flow inbound to the Exchange organization via the Edge Transport server, the queues will
show a DeliveryType of Smart host with the Hub Transport server as the next hop. (See Figure 9 - 22 .)
Figure 9-22
Figure 9-21
Chapter 9: Confi guring the Edge Transport Server Role
263
Edge Cloning
Organizations are not limited to a single Edge Transport server install. You can install and configure
multiple Edge Transport servers in your perimeter network. This is advantageous because it provides
redundancy and enables load balancing if your DNS is configured with multiple Mail Exchanger (MX)
records pointing to one of each Edge Transport server with the same priority.
However, to make sure all the Edge Transport servers deployed in the perimeter network are of
identical configuration, cloned configuration scripts are provided in the Exchange Management Shell to
copy the configuration of one Edge Transport server and duplicate it on as many target Edge Transport
servers as needed.
Pages:
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373