Export (0) Print
Expand All
Expand Minimize

Get-TransportPipeline

 

Applies to: Exchange Server 2013

Topic Last Modified: 2014-04-14

This cmdlet is available only in on-premises Exchange Server 2013.

Use the Get-TransportPipeline cmdlet to view each transport agent and the event with which the transport agent is registered.

Get-TransportPipeline [-DomainController <Fqdn>]

This example returns a list of agents registered in the transport pipeline.

Get-TransportPipeline

This example returns a list of agents registered in the transport pipeline with full details for each transport event.

Get-TransportPipeline | Format-List

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.

NoteNote:
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.

 

Parameter Required Type Description

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that retrieves data from Active Directory.

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.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft