However, to enable Hub Transport servers within an Exchange
organization to communicate, implicit or invisible Send Connectors are automatically created. The Send
Connectors are computed based on the Active Directory site topology and the site where the Hub server
is installed. These implicit connectors are, however, not visible via the Exchange Management Console or
Exchange Management Shell.
To create a Send Connector, use the New-SendConnector cmdlet. Required parameters include
AddressSpaces and name . Three parts make up address spaces: the address space type, the address
itself, and the cost of delivery to that address. It takes the following format: SMTP:ExchangeExchange
.local;10 representing the type, address, and cost, respectively. The Send Connector can accommodate
address space types other than SMTP, such as NOTES, FAX, and so forth. Send Connectors configured
with address spaces that are non - SMTP must be configured to route to a smart host and not use DNS for
resolution and delivery. You can also specify multiple address spaces but they must be enclosed in
double quotation marks and separated by commas.
In configuring a Send Connector, you can also specify its scope. The IsScopedConnector parameter set
to $True indicates that the Send Connector is scoped to the local Active Directory site.
Pages:
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314