How to Deploy RPC over HTTP for the First Time on Exchange Server 2003 SP1 (Front-End/Back-End Scenario)

  • Article

 

This topic explains how to deploy RPC over HTTP in a Microsoft® Exchange Server 2003 Service Pack 1 (SP1) front-end and back-end organization.

Before You Begin

Before you perform the procedures in this topic, confirm the following:

  • You have read System Requirements for RPC over HTTP on Exchange Server 2003.

  • You have one or more front-end servers.

  • You have one or more back-end servers.

  • You have one or more global catalog servers.

  • You have one of the following scenarios:

    • All three roles (front-end, back-end, and global catalog) are applied on separate servers.

    • The front-end role is applied on a separate server. The back-end and global catalog roles are applied on the same server.

      Note

      If your 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 is not a global catalog server, you can experience problems with connectivity to this server.

  • You are running Exchange Server 2003 SP1 on your front-end servers.

  • You are running Exchange Server 2003 on your back-end servers. You can have SP1 installed on your back-end servers, but it is not necessary.

Procedure

To deploy RPC over HTTP for the first time on Exchange Server 2003 SP1, front-end/back-end scenario

  1. Configure all of your Exchange Server 2003 SP1 front-end servers as RPC proxy servers. For detailed steps, see How to Configure a Server as an RPC Proxy Server.

  2. Configure your Exchange Server 2003 back-end servers to act as targets for the RPC proxy servers. For detailed steps, see How to Configure the Back-End Server to Act as a Target for the RPC Proxy Server.

    Note

    Performing this task sets a Microsoft Active Directory® directory service property that will indicate to a front-end server that these back-end servers should be published for RPC over HTTP access. If your topology has multiple global catalog servers, you might want to wait for Active Directory replication to propagate these properties before proceeding to the next step.

  3. Configure the settings on the RPC proxy servers. For detailed steps, see How to Configure the RPC Proxy Server Settings on a Front-End Server in Exchange System Manager.

  4. (Optional) Configure the RPC proxy servers to allow for Secure Sockets Layer (SSL) offloading on a separate server. For detailed steps, see How to Configure the RPC Proxy Server to Allow for SSL Offloading on a Separate Server.

  5. Create a Microsoft Office Outlook® profile for your users to use with RPC over HTTP. For detailed steps, see How to Create an Outlook Profile for Users to Use with RPC over HTTP.

For More Information