Get-TransportPipeline
Applies to: Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
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 2007 organization.
Syntax
Get-TransportPipeline [-DomainController <Fqdn>]
Detailed Description
The Get-TransportPipeline cmdlet enables you to view all the transport agents that are 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 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.
To run the Get-TransportPipeline cmdlet, the account you use must be delegated the following:
- Exchange View-Only Administrator role
To run the Get-TransportPipeline cmdlet on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.
For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
To specify the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to the Active Directory directory service, include the DomainController parameter on the command. The DomainController parameter is not supported on computers that run the Edge Transport server role. The Edge Transport server role reads from and writes to only to the local ADAM instance. |
Input Types
Return Types
Errors
| Error | Description |
|---|---|
|
|
Exceptions
| Exceptions | Description |
|---|---|
|
|
Example
The first example shows how to run the Get-TransportPipeline cmdlet and produce the default view.
The second example shows how to view the output of the Get-TransportPipeline cmdlet in a list format, which lets you view all the transport agents on each event. You do this by piping the Get-TransportPipeline cmdlet to the Format-List cmdlet.
For more information about pipelining, see Pipelining.
For more information about how to work with the output of a command, see Working with Command Output.
Get-TransportPipeline
Get-TransportPipeline | Format-List