Applies to: Exchange Server 2016
This cmdlet is available only in on-premises Exchange Server 2016.
Use the Get-TransportPipeline cmdlet to view each transport agent and the event with which the transport agent is registered.
The Get-TransportPipeline cmdlet enables you to view all the transport agents configured in the following locations:
In the Transport service on a Mailbox server.
In the Front End Transport service on a Client Access server.
On an Edge Transport server in the perimeter network.
|The associated transport service must be started, and at least one e-mail message must be sent through the server since the last service restart before the transport pipeline can be viewed. Only the transport events and agents that were involved in the processing of e-mail messages since the associated service was last restarted are returned.|
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Transport agents" entry in the Mail flow permissions topic.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example,
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.