In the Release To Manufacturing (RTM) version, however, the cloned
configuration did not include the TransportConfig object. Hence, after cloning a target Edge Transport
server, the transport configuration attributes on the target server are different than those on the original
Edge Transport server. In Exchange Server 2007 SP1, the information that is cloned now includes the
TransportConfig object. The TransportConfig object controls server - wide settings for the Edge
Transport server role. This information is written to the intermediate XML file. This way, the transport
Chapter 9: Confi guring the Edge Transport Server Role
241
configuration setting is identical on the target Edge Transport server. The following cmdlets include
some new parameters:
??‘ Start-EdgeSynchronization : This cmdlet now has a new server parameter. This allows an
administrator to start edge synchronization from a remote computer by simply specifying the
Hub Transport server edge synchronization will be run against.
??‘ Update-SafeList : This cmdlet also now has a new includeddomains parameter . One of the
responsibilities of EdgeSync is to replicate safelist aggregation data to the Edge Transport server
role. This safelist is based upon data stored on Outlook user or Outlook Web Access user
mailboxes.
Pages:
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349