[This topic is in progress.]

Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2011-05-05

Use the Get-TransportPipeline cmdlet to view each transport agent and the event with which the transport agent is registered on a computer that has the Edge Transport server role or the Hub Transport server role installed in a Microsoft Exchange Server 2010 organization.

Syntax

Get-TransportPipeline [-DomainController <Fqdn>]

Detailed Description

The Get-TransportPipeline cmdlet enables you to view all the transport agents configured on a Hub Transport server or an Edge Transport server. Each transport agent is listed next to the transport event on which the agent is configured to run.

Note:
The Microsoft Exchange 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 Microsoft Exchange Transport 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 Transport Permissions topic.

Parameters

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 the Edge Transport server role. The Edge Transport server role reads only from the Active Directory Lightweight Directory Services (AD LDS) instance.

Input Types

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.

Return Types

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.

Examples

EXAMPLE 1

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

Copy Code
Get-TransportPipeline

EXAMPLE 2

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

Copy Code
Get-TransportPipeline | Format-List