These scripts are located in the C:\Program Files\Microsoft\Exchange
Server\Scripts directory if you chose the default path for installation.
The clone configuration process involves exporting the source Edge Transport server configuration using
the ExportEdgeConfig.ps1 script to an intermediate XML file. Next you validate whether the settings
exported are valid for the target server by running the ImportEdgeConfig.ps1 script, which checks the
intermediate XML file and creates an answer file. Finally, you clone the target Edge Transport server by
importing the configuration using a combination of the ImportEdgeConfig.ps1 script, the
intermediate XML file, and the answer file.
As mentioned earlier, in Exchange Server 2007 SPI, the information that is cloned now includes the
TransportConfig object.
Transport Agents
In previous versions of Exchange, you could use event sinks to customize some functionality not
available by default in the product, such as adding disclaimers to messages or acting on messages
depending on where the message is located in transport, for example OnMessagePostCategorize ,
OnMessagePreCategorize , OnArrival , and so forth. In Exchange Server 2007, transport event sinks
have been replaced by transport agents. These agents or rules allow you to create customized software
solutions that act on messages as they pass through the transport pipeline on a Hub Transport server or
Edge Transport server.
Pages:
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374