How to Deploy RPC over HTTP for the First Time on Exchange Server 2003 SP1, No Front-End Server
This topic explains how to deploy RPC over HTTP in an organization that is running Microsoft® Exchange Server 2003 Service Pack 1 (SP1).
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 back-end Exchange servers.
You have one or more global catalog servers.
You have one of the following scenarios:
The back-end role and the global catalog role are applied on separate servers.
The back-end role and the global catalog role 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 do not have a front-end server.
You are running Exchange Server 2003 SP1 on all of your Exchange servers.
Note
The Exchange server role and the global catalog server role can be applied on separate servers, or you can have a single server that is both an Exchange back-end server and a global catalog server.
Procedure
To deploy RPC over HTTP for the first time on Exchange Server 2003 SP1 with no front-end server
Configure your Exchange Server 2003 SP1 back-end servers as RPC proxy servers. For detailed steps, see How to Configure a Server as an RPC Proxy Server.
Note
If your back-end servers are clustered, it is not recommended that you make them RPC proxy servers.
Configure your back-end servers that are running on Exchange Server 2003 SP1 as RPC over HTTP back-end servers to validate that the settings are correct. For detailed steps, see How to Configure a Back-End Server That is in a Back-End Only Topology to Use RPC over HTTP.
Configure the RPC over HTTP virtual directory. For detailed steps, see How to Configure the RPC Virtual Directory in IIS.
Configure your back-end servers, which are now RPC proxy servers, to use specified ports for RPC over HTTP. For detailed steps, see how to How to Configure the RPC Proxy Server to Use Specified Ports for RPC over HTTP.
(optional) Configure the RPC proxy server to allow for 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.
Create a Microsoft Office Outlook® profile for 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.
Note
If you have a back-end server that is also a global catalog server, you will be prompted to restart this computer for the changes to take effect.
For More Information
If you are deploying RPC over HTTP for the first time on Exchange Server 2003 SP1, and you do have a front-end server in your organization, see How to Deploy RPC over HTTP for the First Time on Exchange Server 2003 SP1 (Front-End/Back-End Scenario)
If you are deploying RPC over HTTP for the first time on Exchange Server 2003 and have not installed Service Pack 1 on your Exchange servers, see one of the following topics:
If you have already deployed RPC over HTTP in an Exchange Server 2003 organization and are upgrading that organization from Exchange Server 2003 to Exchange 2003 SP1, see How to Upgrade an Exchange Server 2003 RPC over HTTP Deployment to Exchange Server 2003 SP1
If you want to add another Exchange Server 2003 back-end server to your organization after you have deployed RPC over HTTP, see Adding a Back-End Server to an RPC over HTTP Deployment
If you want help with troubleshooting RPC over HTTP communications, see Troubleshooting RPC over HTTP Communications.