This step was shown earlier in this
chapter in the section on ??? Preparing the Edge Transport Server. ???
At the end of this scenario, the Send Connectors shown in Figure 9 - 15 are created automatically
on the Hub Transport server by the edge subscription process. No other Receive Connector is
created other than the defaults.
Figure 9-15
Verifying Configuration
There are a couple of things to observe after the edge subscription and edge synchronization process
completes. You can use the Start-EdgeSynchronization cmdlet to ensure that the synchronization is
kicked off and the Test-EdgeSynchronization cmdlet to view the synchronization status. The
Start-EdgeSynchronization cmdlet is shown in Figure 9 - 16 .
Some key items to always check here after running the Start-EdgeSynchronization cmdlet are the
result, type, and failure details as well as items scanned or deleted. These provide an insight into
whether changes made are getting updated on the Edge Transport server. For example, if you create a
new user, you can determine by the items scanned in the Recipients type to see if it was incremented.
Part II: Working with Server Roles
258
Figure 9-16
Another way to verify if a user created was replicated to the ADAM database is to use the
Test-EdgeSynchronization cmdlet.
Pages:
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371