Del via

Configure Hub Transport Server Properties

  • Artikkel

 

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

The property configuration of a transport server running Microsoft Exchange Server 2010 determines how that server processes messages. The transport server settings that you configure on a Hub Transport server apply only to that specific server.

Looking for other management tasks related to configuring Hub Transport server properties? Check out Managing Transport Servers.

What Do You Want to Do?

  • Use the EMC to configure the properties of a Hub Transport server

  • Use the Shell to configure the properties of a Hub Transport server

Use the EMC to configure the properties of a Hub Transport server

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

  1. In the console tree, navigate to Server Configuration > Hub Transport.

  2. In the result pane, right-click the Hub Transport server you want to configure, and then select Properties.

  3. On the General tab, you can view general information about the server:

    • Version This field displays the version of Exchange installed on the server.

    • Edition This field displays the Exchange Server edition. The edition is either Standard Edition or Enterprise Edition.

    • Role(s) This field displays the Exchange server roles installed on the server.

    • Product ID This field displays the product ID for the Exchange server. If you haven't yet entered the product key for the server, the product ID displayed is Unlicensed. To license an unlicensed version of Exchange, see Enter Product Key.

    • Modified This field displays the last date and time that a configuration change was made on this server.

  4. On the System Settings tab, view the domain controller servers and global catalog servers. You can also enable an error reporting feature:

    • Domain controller servers being used by Exchange This read-only box displays a list of domain controller servers used by the Exchange server.

      Note

      This box isn't available on Edge Transport servers.

    • Global catalog servers being used by Exchange This read-only box displays a list of global catalog servers used by the Exchange server.

      Note

      This box isn't available on Edge Transport servers.

    • Automatically send fatal service error report to Microsoft Select this check box if you want to enable the error reporting feature and automatically send an error report to Microsoft in the event of a fatal error.

      If you enable the error reporting feature, information about fatal service errors is sent to Microsoft over encrypted channels. The information is used to improve Microsoft products.

      When this feature is enabled and the issue reported has a known solution, the server receives feedback from Microsoft. This feedback contains a link to information that may help resolve the problem.

  5. On the Customer Feedback Options tab, you can enroll the selected server into the Customer Experience Improvement Program. For more information, see Opt-in or Opt-out of the Customer Experience Improvement Program.

  6. Use the External DNS Lookups tab to specify whether to use the DNS servers that are configured on a network adapter installed on this server or to use specific DNS servers when resolving the addresses of mail servers for external mail delivery. External DNS servers are used by Send connectors that are configured to use the external DNS lookup configuration on the transport server. When messages are routed to these Send connectors, the external DNS lookup settings that are configured for the source servers are used to resolve IP addresses for the delivery destination.

    You can choose one of the following options:

    • Use network card DNS settings   To select an installed network adapter from the list, select Use network card DNS settings, and then select a network adapter from the drop-down list. The server then uses the DNS servers configured on that network adapter. The default setting is All Available IPv4. If you select this setting, the server uses the DNS servers configured on all the adapters on that server.

    • Use these DNS servers   To have the server select from a list of manually entered DNS servers to query when resolving a remote server, select Use these DNS servers. To add a server to the list, type the IP address of the external DNS server, and then click Add. To change the IP address of a previously added DNS server, select that server, and then click Edit. To remove a previously added DNS server, select that server, and then click Remove icon.

  7. Use the Internal DNS Lookups tab to specify whether to use the DNS servers that are configured on a network adapter installed on this server or to use specific DNS servers when resolving the addresses of mail servers for internal mail delivery. Internal DNS servers are used to resolve IP addresses for servers inside your organization.

    You can choose one of the following options:

    • Use network card DNS settings   To select an installed network adapter from the list, select Use network card DNS settings, and then select a network adapter from the drop-down list. The server then uses the DNS servers configured on that network adapter. The default setting is All Available IPv4. If you select this setting, the server uses the DNS servers configured on all the adapters on that server.

    • Use these DNS servers   To have the server select from a list of manually entered DNS servers to query when it's resolving an internal server, select Use these DNS servers. To add a server to the list, type the IP address of the internal DNS server, and then click Add. To change the IP address of a previously added DNS server, select that server, and then click Edit. To remove a previously added DNS server, select that server, and then click Remove icon.

  8. Use the Limits tab to specify the number of times that the server retries message delivery, to set notification for undelivered messages, and to specify connection restrictions.

    • Outbound connection failure retry interval (minutes) Select this option to specify the retry interval for subsequent connection attempts to a remote server where earlier connection attempts as specified by the transient failure retry attempts and the transient failure retry interval have failed. The valid input range is 1 minute to 28800 minutes (20 days). We recommend that you don't modify the default value unless Microsoft Customer Service and Support has advised you to do this. The default value is 10 minutes.

    • Transient failure retry interval (seconds) Select this option to specify the interval between each connection attempt specified by the Transient failure retry attempts option. The valid input range is 1 second to 43200 seconds (12 hours). The default value is 300 seconds (5 minutes).

    • Transient failure retry attempts Select this option to specify the maximum number of times that a server immediately retries when it encounters a connection failure with a remote server. The default value is 6. The valid input range is 0 to 15. When this parameter is set to 0, the server doesn't immediately try to reconnect.

    • Maximum time since submission (days) Select this option to specify the expiration time-out for a particular message. If a message remains in the queue for longer than this period of time, the message is returned to the sender as a hard failure. The default value is 2 days. The valid input range is 1 day to 90 days.

    • Notify sender when message is delayed more than (hours) Select this option to specify how long the server waits before it generates a delivery status notification (DSN) that notifies the sender of a delivery delay. The default value is 4 hours. The valid input range is 1 hour to 720 hours (30 days).

    • Maximum concurrent outbound connections Select this option to specify the maximum number of outgoing connections that can be open at a time. If the connection limit is reached, the server doesn't initiate new connections until the number of current connections decreases. The default value is 1000. The valid input range is 1 to 2147483647. To disable this restriction, clear the check box next to Maximum concurrent outbound connections.

    • Maximum concurrent outbound connections per domain Select this option to specify the maximum number of concurrent connections to any single domain. The default value is 20. The valid input range is 1 to 2147483647. To disable this restriction, clear the check box next to Maximum concurrent outbound connections per domain.

  9. Use the Log Settings tab to enable or disable message tracking, enable or disable connectivity logging, and to view or change the path for the message tracking logs, connectivity logs, Send connector protocol logs, and Receive connector protocol logs. On the Log Settings tab, you can view or set the following options:

    • Enable message tracking log   By default, message tracking is enabled on Hub Transport and Edge Transport servers. To disable message tracking, clear the check box next to Enable message tracking log. To enable message tracking, select the check box next to Enable message tracking log.

    • Message tracking log path   This field displays the current location of the message tracking logs. By default, the message tracking logs are stored at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\MessageTracking. To change the location of the message tracking logs, type the path to the new log location. Before you can change the path, message tracking must be enabled.

    • Enable connectivity log   By default, connectivity logging is disabled on Hub Transport and Edge Transport servers. To enable connectivity logging, select the check box next to Enable connectivity log. To disable connectivity logging, clear the check box next to Enable connectivity log.

    • Connectivity log path   This field displays the current location of the connectivity logs. By default, the connectivity logs are stored at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\Connectivity. To change the location of the connectivity logs, type the path to the new log location. Before you can change the path, connectivity logging must be enabled.

    • Send protocol log path   This field displays the current location of the Send connector protocol logs. By default, the Send connector protocol logs are stored at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend. All the Send connectors that are configured on the Edge Transport server share the same protocol logs. By default, protocol logging is disabled on all Send connectors.

      To change the location of the Send connector protocol logs, type the path to the new log location.

    • Receive protocol log path   This field displays the current location of the Receive connector protocol logs. By default, the Receive connector protocol logs are stored at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive. All the Receive connectors that are configured on the Edge Transport server share the same protocol logs. By default, protocol logging is disabled on all Receive connectors.

      To change the location of the Receive connector protocol logs, type the path to the new log location.

Use the Shell to configure the properties of a Hub Transport server

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

You use the Set-TransportServer cmdlet to configure the properties of a Hub Transport server. Although the EMC allows you to configure the most commonly used properties of a Hub Transport server, the Set-TransportServer cmdlet allows you to configure all the properties of a Hub Transport server. The following examples demonstrate how you can use the Shell to configure the most common properties of a Hub Transport server. For more information about the possible configuration options, see Managing Transport Servers.

This example configures a Hub Transport server to use a specific list of DNS servers for external DNS lookups instead of the DNS servers configured on the adapters installed on that server.

Set-TransportServer Hub01 -ExternalDNSAdapterEnabled $false -ExternalDNSServers {192.168.1.1, 192.168.1.2}

This example enables connectivity logging on the Hub Transport server and configures it to store the connectivity log files in the C:\SMTP Logs folder.

Set-TransportServer Hub01 -ConnectivityLogEnabled $true -ConnectivityLogPath "C:\SMTP Logs"

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

 © 2010 Microsoft Corporation. All rights reserved.