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 location of the routing table logs.

By default, the routing table logs are stored in the C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\Routing directory. The directory must be local to the Exchange 2010 computer.

This example changes the location of the routing table log to C:\Routing Table on the Exchange 2010 computer Exchange01.

	Copy Code
Set-TransportServer Exchange01 -RoutingTableLogPath "C:\Routing Table"

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

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.

The routing table is recalculated and logged after a routing configuration change, or after a specified time interval has passed if no changes are detected. By default, the routing table is automatically recalculated every 12 hours.

The interval for automatic recalculation of the routing table is controlled by the RoutingConfigReloadInterval parameter in the EdgeTransport.exe.config file located in C:\Program Files\Microsoft\Exchange Server\V14\Bin. The EdgeTransport.exe.config file is an XML application configuration file associated with the EdgeTransport.exe file. EdgeTransport.exe and MSExchangeTransport.exe are the executable files used by the Microsoft Exchange Transport service. This service runs on every Hub Transport server or Edge Transport server. Changes made to the EdgeTransport.exe.config file are applied after the Microsoft Exchange Transport service is restarted.

The following example shows the typical structure of the EdgeTransport.exe.config file.

<configuration>

<runtime>

<gcServer enabled="true" />

</runtime>

<appSettings>

<add key=" Configuration Option " value=" Value " />

...

</appSettings>

</configuration>

You can add new configuration options or modify existing configuration options in the <appSettings> section. Many available configuration options are unrelated to the routing table. Any configuration options that don't involve the routing table are outside the scope of this topic.

Note:
The parameter names in the <add key=../> section are case sensitive.

1. Open the following file by using Notepad: C:\Program Files\Microsoft\Exchange Server\ V14\Bin\EdgeTransport.exe.config.
   
   
2. Modify the following line in the <appSettings> section.
   
   

   	Copy Code
   <add key="RoutingConfigReloadInterval" value="<interval>" />

   This example changes the interval for automatic recalculation of the routing table to 10 hours, by modifying the RoutingConfigReloadInterval parameter.
   
   

   	Copy Code
   <add key="RoutingConfigReloadInterval" value="10:00:00" />

3. Save and close the EdgeTransport.exe.config file.
   
   
4. Restart the Microsoft Exchange Transport service.
   
   

To specify an age value, enter it as a time span, as follows: hh:mm:ss, where h = hours, m = minutes, and s = seconds.

The routing table will be recalculated and logged earlier than the value specified by the RoutingConfigReloadInterval parameter if any of the following conditions occur:

• A routing configuration change is detected. For example, a Send connector or a Receive connector is added, removed, or modified, or the 6 hour Kerberos token renewal occurs.
  
  
• The Microsoft Exchange Transport service is started.
  
  

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 maximum size of the routing table log directory.

By default, the maximum size for the whole routing table log directory is 50 megabytes (MB). Circular logging deletes the oldest routing table log files if either of the following conditions is true:

• The routing table log directory reaches its specified maximum size.
  
  
• A routing table log file reaches its specified maximum age.
  
  

This example sets the maximum size of the routing table log directory to 70 MB on the Exchange 2010 computer Exchange01.

	Copy Code
Set-TransportServer Exchange01 -RoutingTableLogMaxDirectorySize 70MB

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

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 maximum age of the routing table logs.

By default, the maximum age for any routing table log file is 7 days. Circular logging deletes the oldest routing table log files if either of the following conditions is true:

• The routing table log directory reaches its specified maximum size.
  
  
• A routing table log file reaches its specified maximum age.
  
  

To configure the maximum age of the routing table logs, use the following syntax.

	Copy Code
Set-TransportServer <Identity> -RoutingTableLogMaxAge <Age>

This example changes the maximum age of a routing table log file to 45 days on the Exchange 2010 computer Exchange01.

	Copy Code
Set-TransportServer Exchange01 -RoutingTableLogMaxAge 45.00:00:00

To specify an age value, enter it as a time span, as follows: dd.hh:mm:ss, where d = days, h = hours, m = minutes, and s = seconds. The valid input range for this parameter is 00:00:00 through 24855.03:14:07. Setting the value of the RoutingTableLogMaxAge parameter to 00:00:00 prevents the automatic removal of routing table log files because of their age.

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