This is shown in Figure 9 - 17 .
When this cmdlet is run, it displays some important information. The name specified is always that of
the Edge Transport server and the LeaseHolder is the Hub Transport server. The ConnectionResult
determines whether the test run was successful. If it is not, the FailureDetail property is populated
with the status of the failure.
Chapter 9: Confi guring the Edge Transport Server Role
259
Figure 9-17
Also in Figure 9 - 17 , we used the VerifyRecipient parameter of the Test-EdgeSynchronization
cmdlet to verify whether Trainee19 has been replicated to the Edge Transport server. The status
Synchronized for the RecipientStatus tells us that it has.
Another way to verify that the initial edge synchronization completed is to notice the
OU= OU=MSExchangeGateway , CN=Recipients hierarchy on the ADAM database populated as
shown in Figure 9 - 18 .
Sometimes due to a non delivery report or Recipient failure event logged on the Edge Transport server, it
may be necessary to determine which Recipient a specific CN points to. In the example in Figure 9 - 19 , in
ADAM we select a CN for a Recipient 6ff45354-9502-4771-b178-7c97a864cdef .
Part II: Working with Server Roles
260
Figure 9-18
Figure 9-19
Chapter 9: Confi guring the Edge Transport Server Role
261
You can simply take this information to a domain controller in the Active Directory site and enter the
search filter shown in Figure 9 - 20 .
Pages:
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372