Exchange System Manager on the Back-End Server

  • Article

 

In Microsoft® Exchange Server 2003, Exchange System Manager can help configure Exchange back-end servers as RPC over HTTP back-end servers. When you select an Exchange server to be an RPC over HTTP back-end server, Exchange System Manager performs the following actions:

  • It verifies that the Exchange server and operating system support RPC over HTTP by verifying that you have installed Exchange Server 2003 and Microsoft Windows Server™ 2003.

  • It verifies that you have configured the Microsoft Exchange Information Store service and system attendant ports correctly for RPC over HTTP. If you have not configured the Microsoft Exchange Information Store service and system attendant ports correctly for RPC over HTTP, Exchange System Manager sets the ports and prompts the administrator to restart any services that require restarts.

  • If the back-end server is also a global catalog server, Exchange System Manager also sets the RPC directory port on the global catalog server to the correct value (6004). Exchange System Manager then prompts the administrator to restart the server.

    Note

    If your RPC over HTTP back-end server is also a domain controller, it is recommended that you make this domain controller a global catalog server. If an RPC over HTTP back-end server is a domain controller but not a global catalog server, you may experience problems with connectivity to this server.

  • If the back-end server is part of a cluster, Exchange System Manager tries to verify the Microsoft Exchange Information Store service port and the proxy and referral service ports of DSProxy.

    Exchange System Manager sets the Microsoft Exchange Information Store service port and the proxy and referral service ports of DSProxy on all the physical nodes of the cluster if they are not set correctly.

    If Exchange System Manager cannot access a node of the cluster, Exchange System Manager instructs the administrator to examine the node manually. For example, if one of the nodes is down for maintenance, Exchange System Manager instructs the administrator to examine the node manually.

  • If you have not configured any front-end servers as RPC over HTTP front-end servers, Exchange System Manager warns the administrator that a front-end server must be configured as an RPC over HTTP front-end server for Exchange System Manager to publish the back-end server in the ValidPorts registry entry on the RPC proxy server automatically.

After Exchange System Manager completes verification, Exchange System Manager sets a value on the Exchange server directory object to identify the server as an RPC over HTTP back-end server. Exchange System Manager now displays the server as an RPC over HTTP back-end server in the Exchange System Manager user interface.