You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Transport agents" entry in the Transport Permissions topic.

Note:
You can't use the EMC to modify the priority of the Content Filter agent.

This example sets the priority value of the Content Filter agent to 3. Because the Edge Rule agent by default uses priority value 3, its priority value is increased to 4.

1. Use the Shell to set the priority value of the Content Filter agent to 3.
   
   

   	Copy Code
   Set-TransportAgent "Content Filter Agent" -Priority 3

2. Stop the Microsoft Exchange Transport service.
   
   

   	Copy Code
   Net Stop MSExchangeTransport

3. Start the Microsoft Exchange Transport service.
   
   

   	Copy Code
   Net Start MSExchangeTransport

For detailed syntax and parameter information, see Set-TransportAgent.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Transport agents" entry in the Transport Permissions topic.

Note:
You can't use the EMC to verify transport agent priority order.

You can verify the transport agent priority order by sending a test message through the Edge Transport server that you just configured. Then you can use the Get-TransportPipeline cmdlet to view the transport agent priority order. You must send a message through the Edge Transport server because the Get-TransportPipeline cmdlet retrieves information about the transport pipeline that's built dynamically every time a message is sent.

This example verifies the transport agent priority order.

1. Send a message through the Edge Transport server that you just configured.
   
   
2. Run the following command.
   
   

	Copy Code
Get-TransportPipeline

The output produced by this procedure will resemble the following example. In the following example, the Content Filter agent is listed before the Edge Rule agent on the OnEndOfData SMTP event. This indicates that the Content Filter agent is now being applied to messages before the Edge Rule agent on the OnEndOfData SMTP event.

Copy Code

Event : OnConnectEvent TransportAgents : {Connection Filtering Agent, Protocol Analysis Agent} Event : OnHeloCommand TransportAgents : {} Event : OnEhloCommand TransportAgents : {} Event : OnAuthCommand TransportAgents : {} Event : OnEndOfAuthentication TransportAgents : {} Event : OnMailCommand TransportAgents : {Connection Filtering Agent, Sender Filter Agent} Event : OnRcptCommand TransportAgents : {Connection Filtering Agent, Address Rewriting Inbound Agent, Recipient Filter Agent} Event : OnDataCommand TransportAgents : {} Event : OnEndOfHeaders TransportAgents : {Connection Filtering Agent, Address Rewriting Inbound Agent, Sender Id Agent, Sender Filter Agent, Protocol Analysis Agen t} Event : OnEndOfData TransportAgents : {Content Filter Agent, Edge Rule Agent, Protocol Analysis Age nt, Attachment Filtering Agent} Event : OnHelpCommand TransportAgents : {} Event : OnNoopCommand TransportAgents : {} Event : OnReject TransportAgents : {Protocol Analysis Agent} Event : OnRsetCommand TransportAgents : {Protocol Analysis Agent} Event : OnDisconnectEvent TransportAgents : {Protocol Analysis Agent} Event : OnSubmittedMessage TransportAgents : {Address Rewriting Outbound Agent} Event : OnRoutedMessage TransportAgents : {Address Rewriting Outbound Agent}

For detailed syntax and parameter information, see Get-TransportPipeline.