How to Deploy RPC over HTTP for the First Time on Exchange Server 2003, No Front-End Server, Back-End on Global Catalog Server

Collapse All

Topic Last Modified: 2006-04-27

This topic explains how to deploy RPC over HTTP in a Microsoft® Exchange Server 2003 organization that has the following characteristics:

The Exchange organization does not have a front-end server.
The Exchange organization has at least one back-end server that is also a global catalog server.

Before You Begin

Before you perform the procedure in this topic:

It is important that you first read System Requirements for RPC over HTTP on Exchange Server 2003.

Confirm the following:

At least one of your back-end servers is located on the same computer as a global catalog 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 without service packs on all of your Exchange servers.

Procedure

To deploy RPC over HTTP for the first time on Exchange Server 2003, no front-end server, back-end on a global catalog server

Configure an Exchange Server 2003 back-end server as an RPC proxy server. For detailed steps, see How to Configure a Server as an RPC Proxy Server.
Configure the RPC virtual directory. For detailed steps, see How to Configure the RPC Virtual Directory in IIS.
Configure the RPC proxy server to use specified ports for RPC over HTTP. For detailed steps, see How to Configure the RPC Proxy Server to Use Specified Ports for RPC over HTTP.
Set the NT Directory Services (NTDS) port on all global catalog servers that act as Exchange Server 2003 back-end servers. For detailed steps, see How to Set the NTDS Port on a Global Catalog Server Acting as an Exchange Server 2003 Back-End Server.
(optional) Configure the RPC proxy server 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.
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

If you are deploying RPC over HTTP for the first time on Exchange Server 2003, and you do have a front-end server in your organization, see one of the following topics:
- How to Deploy RPC over HTTP for the First Time on Exchange Server 2003, Front-End/Back-End Scenario
- How to Deploy RPC over HTTP for the First Time on Exchange Server 2003, Front-End/Back-End Scenario, Back End on Global Catalog Server
If you are deploying RPC over HTTP for the first time on Exchange Server 2003, and you do not have a front-end server in your organization, and you do not have a server that is both a back-end server and a global catalog server, see the following topic:
- How to Deploy RPC over HTTP for the First Time on Exchange Server 2003, No Front-End Server
If you are deploying RPC over HTTP for the first time on Exchange Server 2003 SP1, see one of the following topics:
- How to Deploy RPC over HTTP for the First Time on Exchange Server 2003 SP1 (Front-End/Back-End Scenario)
- How to Deploy RPC over HTTP for the First Time on Exchange Server 2003 SP1, No Front-End Server
If you have already deployed RPC over HTTP in an Exchange Server 2003 topology and are upgrading that topology to Exchange Server 2003 SP1, see How to Upgrade an Exchange Server 2003 RPC over HTTP Deployment to Exchange Server 2003 SP1.
If you want help with troubleshooting RPC over HTTP communications, see Troubleshooting RPC over HTTP Communications.