Export (0) Print
Expand All

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

 

Topic Last Modified: 2006-04-27

This topic explains how to deploy RPC over HTTP in a Microsoft® Exchange Server 2003 organization that does not have a front-end server.

Before you perform the procedures in this topic:

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

  • Confirm the following:

    • You have one or more back-end servers.

    • You have one or more global catalog servers.

    • You do not have a front-end server.

    • The back-end server and global catalog server roles are applied on separate servers.

    • You are running Exchange Server 2003 without service packs on all of your Exchange servers.

  1. Configure an Exchange Server 2003 back-end server as an RPC proxy server. For detailed information, see How to Configure a Server as an RPC Proxy Server.

  2. Configure the RPC virtual directory. For detailed information, see How to Configure the RPC Virtual Directory in IIS.

  3. Configure the RPC proxy server to use specified ports for RPC over HTTP. For detailed information, see How to Configure the RPC Proxy Server to Use Specified Ports for RPC over HTTP.

  4. (optional) Configure the RPC proxy server to allow for Secure Sockets Layer (SSL) offloading on a separate server. For detailed information, 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 information, see How to Create an Outlook Profile for Users to Use with RPC over HTTP.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft