• Use the EMC to configure server properties
  
  
• Use the Shell to configure server properties
  
  

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

1. In the console tree, navigate to the forest you want, and then click Server Configuration.
   
   
2. In the result pane, click the server that you want to configure.
   
   
3. In the action pane, click Properties.
   
   
4. 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.
     
     
5. 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.
     
     
6. 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.
   
   
7. 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 .
     
     
8. 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 .
     
     
9. 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.
     
     
10. 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.
      
      
11. Use the Outlook Anywhere tab to view or configure Outlook Anywhere settings. This tab is available only on servers that have the Client Access server role installed.
    
    
    • Status   This read-only field displays whether Outlook Anywhere is enabled or disabled for the server.
      
      
    • External host name   Use this text box to type the external host name or URL for your organization. Users will use this name to connect to the Exchange server by using Outlook Anywhere.
      
      
    • Client authentication method   There are three authentication options available for Outlook Anywhere.
      
      Basic authentication   Click this button to use Basic authentication. Basic authentication sends the user's user name and password in clear text. Basic authentication also requires the user to enter their domain, user name, and password every time they connect to the Client Access server.
      
      NTLM authentication   Click this button to use NTLM authentication. NTLM authentication is also known as Integrated Windows authentication. When NTLM authentication is used, the user's credentials aren't sent over the network. Instead, the client computer and the server exchange hashed values of the user's credentials. NTLM can also use the current Microsoft Windows operating system logon information.
      
      Even though it is more secure, NTLM may not work with firewalls that examine and modify traffic. For more information about whether you can use NTLM with your firewall, see your firewall manufacturer's documentation. We recommend that you choose NTLM authentication with SSL when you're using an advanced firewall server such as Microsoft Internet Security and Acceleration (ISA) Server 2006. ISA Server 2006 allows NTLM authentication to be used with Outlook Anywhere.
      
      Negotiate Ex authentication   Do not click this button. Negotiate Ex authentication is an authentication type reserved for future Microsoft use and shouldn't be used. Use of this setting will cause authentication to fail.
      
      
    • Allow secure channel (SSL) offloading   Select this check box if you will be using a separate server to handle Secure Sockets Layer (SSL) encryption and decryption. When you use SSL offloading, the firewall in front of the Client Access server ends the SSL session and then establishes a new non-SSL session to the Client Access server.
      
      
12. On the Messaging Records Management tab, configure the schedule for the Managed Folder Assistant. The Managed Folder Assistant is an Exchange Mailbox Assistant that places the managed folders that you have created into users' mailboxes and applies managed content settings to managed folders. When the Managed Folder Assistant is running, it processes all the mailboxes on a server. If the Managed Folder Assistant doesn't finish processing the mailboxes on the server in the time that you specified, it automatically resumes processing where it left off the next time it runs. There is one Managed Folder Assistant for each server. To learn more, see Configure the Managed Folder Assistant.
    
    
    • Schedule the Managed Folder Assistant   Use this box to schedule the Managed Folder Assistant or to prevent it from running. The following options are available:
      
      Use Custom Schedule   Select this option to configure the Managed Folder Assistant to run at specified times. If you select UseCustom Schedule, you must also click Customize to set a schedule. There is no default schedule.
      
      Never Run   Select this option to prevent the Managed Folder Assistant from running.
      
      
    • Customize   Click this button to open the Schedule dialog box and set a schedule for the Managed Folder Assistant. To set the schedule, click the time grid in the dialog box. The Managed Folder Assistant runs during the time slots that you select, which are marked in blue. You can select the same time slot every day by clicking a column header for a specific time slot. You can select an entire day by clicking the name of that day.
      
      The default time slot for the grid is one hour. For finer control, you can change the schedule grid to 15 minute intervals by clicking 15 Minutes. Scheduled intervals must be at least 15 minutes apart.
      
      
13. Use the UM Settings tab to view and configure settings for the Unified Messaging (UM) server. This tab is available only on servers that have the Unified Messaging server role installed.
    
    
    • Associated Dial Plans   Use this box to view the UM dial plans associated with the Unified Messaging server. When you install the Unified Messaging server role on a computer running Exchange Server 2010, the server is left in an enabled state. However, for the UM server to answer and process incoming calls, you must also associate a UM dial plan with the UM server. Click Add to select a UM dial plan.
      
      An Exchange 2010 UM server can be associated with multiple UM dial plans that have different Voice over IP (VoIP) security settings at the same time. After you associate the UM server with a UM dial plan, the UM server will process incoming calls for users who are associated with the UM dial plan.
      
      
    • Prompt languages   Use this text box to view the languages supported by the UM server. The languages listed in this box are the languages or language packs installed on the UM server.
      
      By default, when you install the Unified Messaging server role, the U.S. English (en-US) language is installed even if you chose to install other languages when you installed Exchange 2010, and it can't be removed. However, after you've downloaded the appropriate UM language packs, you can add language packs for UM by using the Setup.com /AddUMLanguagePack or run the<UMLanguagePack>.exe installation program after you've downloaded the UM language pack from Exchange Server 2010 UM Language Packs. For details about how to add UM languages, see Managing Unified Messaging Servers.
      
      
    • Startup mode   Use this list to specify whether the Microsoft Exchange Unified Messaging service on a Unified Messaging server will start in TCP, TLS, or Dual mode. If the UM server is being added to UM dial plans that have different security settings, you should select Dual mode. In Dual mode, the UM server can listen on ports 5060 and 5061 simultaneously. If you change the startup mode, you must restart the Microsoft Exchange Unified Messaging service for the change to take effect.
      
      
    • Maximum concurrent calls   Use this box to specify the number of concurrent incoming voice call connections that the UM server will accept. When you increase the number of concurrent connections on a UM server, more system resources are required than if you decrease the number of concurrent voice call connections. Decreasing this setting is especially important on low-end, slower UM servers.
      
      The range for this setting is from 0 through 200. The default setting is 100. There are performance counters that you can use to monitor the current number of voice calls connected to a UM server.
      
      

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the"Shell infrastructure permissions" section in the Exchange and Shell Infrastructure Permissions topic.

This example turns off error reporting for the server.

	Copy Code
Set-ExchangeServer -Identity TestServer.Contoso.com -ErrorReportingEnabled: $False

This example enrolls this server into the Customer Experience Improvement Program (CEIP).

	Copy Code
Set-ExchangeServer -Identity TestServer.Contoso.com -CustomerFeedbackEnabled $true