Some are discussed later in more detail.
??‘ Get-EdgeSubscription
??‘ New-EdgeSubscription
??‘ Remove-EdgeSubscription
??‘ Start-EdgeSynchronization
??‘ Test-EdgeSynchronization
??‘ Get-AcceptedDomain
??‘ Set-AcceptedDomain
??‘ New-AcceptedDomain
??‘ Remove-AcceptedDomain
??‘ Get-RemoteDomain
??‘ Set-RemoteDomain
??‘ New-RemoteDomain
??‘ Remove-RemoteDomain
??‘ Get-AdSite
??‘ Get-SendConnector
??‘ Set-SendConnector
??‘ New-SendConnector
??‘ Remove-SendConnector
??‘ Get-ReceiveConnector
??‘ Set-ReceiveConnector
??‘ New-ReceiveConnector
??‘ Remove-ReceiveConnector
??‘ Disable-TransportAgent
??‘ Enable-TransportAgent
??‘ Get-TransportAgent
??‘ Set-TransportAgent
??‘ Uninstall-TransportAgent
Chapter 9: Confi guring the Edge Transport Server Role
237
Overview of the Edge Transport
Server Role
The actual focus of this role is relaying inbound and outbound messages to and from an Exchange
organization while providing message hygiene and security. It is essentially an SMTP relay server.
Unlike the Hub Transport server role, the Edge Transport server role does not require direct access to
Active Directory. It is installed in a perimeter network on either a Windows member server or
workstation with no domain membership. Information required by the Edge Transport server to perform
its functions is provided in the Active Directory Application Mode (ADAM) directory service.
Pages:
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341