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

Topic Last Modified: 2012-07-23

You can use the Shell to configure the properties of the Replay directory in Microsoft Exchange Server 2010. By default, the Replay directory exists on every computer running Exchange 2010 that has the Hub Transport server role or the Edge Transport server role installed. Correctly formatted e-mail message files that you copy to the Replay directory are submitted for delivery. The Replay directory receives messages from non-SMTP foreign gateway servers and resubmits messages that administrators export from the queues of Exchange 2010 servers.

Looking for other management tasks related to managing connectors? Check out Managing Connectors.

Use the Shell to configure the Replay directory location

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

Note:
You can't use the EMC to configure the Replay directory.

Use the ReplayDirectoryPath parameter of the Set-TransportServer cmdlet to configure the location of the Replay directory. By default, the Replay directory is located at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Replay. The directory must be local to the computer running Exchange 2010.

This example changes the Replay directory location to C:\Replay Directory on server Exchange01.

Copy Code 
Set-TransportServer Exchange01 -ReplayDirectoryPath "C:\Replay Directory"

When changing the location of the Replay directory, you need to be aware of the following:

  • Setting the value of the ReplayDirectoryPath parameter to $null disables the Replay directory.

  • The directory specified by the ReplayDirectoryPath parameter and the PickupDirectoryPath parameter can't be the same.

  • Changing the location of the Replay directory doesn't copy any existing message files from the old Replay directory to the new Replay directory. The new Replay directory location is active almost immediately after the configuration change, but any existing message files are left in the old Replay directory.

You also need to make sure that the permissions are configured correctly on the new location of the Replay directory. To learn more about the permission requirements, see "Permissions for the Pickup and Replay Directories" in Understanding the Pickup and Replay Directories.

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

Use the Shell to configure the maximum rate of message processing for the Replay directory

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.

Note:
You can't use the EMC to configure the Replay directory.

The rate of message processing for both the Pickup directory and the Replay directory is specified by the PickupDirectoryMaxMessagesPerMinute parameter of the Set-TransportServer cmdlet. By default, the Replay directory can process messages at a rate of 100 messages per minute. Limiting the rate of message processing helps prevent performance issues caused by processing numerous messages in the Replay directory.

This example increases the maximum rate of message processing for the Pickup and Replay directories to 200 messages per minute on server Exchange01.

Copy Code 
Set-TransportServer Exchange01 -PickupDirectoryMaxMessagesPerMinute 200

The valid input range for the PickupDirectoryMaxMessagesPerMinute parameter is from 1 through 20000.

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