If performed
after the edge subscription, this information does not get updated for the organization without
re - subscribing the Edge Transport server.
4. Configure Accepted and Remote Domains: This step must be performed on the Hub Transport
server and prepares the information to be propagated to the Edge Transport server. This step is
discussed further in the section ??? Preparing the Hub Transport Server ??? later in this chapter.
5. Export Edge Subscription: This step is performed on an Edge Transport server and generates a
subscription file. This subscription file contains a public - private key pair as well as ADAM
bootstrap credentials that will be used to set up the initial synchronization between the Edge
Transport and Hub Transport servers. This file must be manually copied over to the Hub
Transport server and imported. The New-EdgeSubscription cmdlet is used to perform
these tasks. The syntax used for this cmdlet is New-EdgeSubscription -FileName
???c:\EdgeSubscription01.xml??? .
Any filename can be specified but it must have an .xml extension. Figure 9 - 8 shows what you
will see when this cmdlet is run.
The process of generating this subscription file also creates an ExchangeSync Replication Account
(ESRA) in the ADAM database, which will be used for the initial synchronization.
Pages:
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363