Export (0) Print
Expand All

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

 

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 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:

    • You have one or more back-end servers.

    • You have one or more global catalog servers.

    • You do not have a front-end server.

    • At least one of your back-end servers is located on the same computer as a global catalog server.

      noteNote:
      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.

  1. 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.

  2. Configure the RPC virtual directory. For detailed steps, 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 steps, see How to Configure the RPC Proxy Server to Use Specified Ports for RPC over HTTP.

  4. 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.

  5. (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.

  6. 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.

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

Community Additions

ADD
Show:
© 2014 Microsoft