configure RPC over HTTP - Exchange 2003
RPC over HTTPS: Server Configuration
Required Components Setup
Install the "RPC over HTTP Proxy" on the server that is hosting the public facing web site. If this is a front-end/back-end then it is the front-end server. If if it a single server, then it will be the Exchange server.
You will find RPC Proxy in Add/remove Programs --> Add/Remove Windows Components --> Networking Services
Configure SSL and Certificate
if you have a web certificate you can contniue if not create a web certificate http://blogs.microsoft.co.il/blogs/dand/archive/2009/07/19/enabling-owa-2003-ssl-using-your-own-certificate-authority.aspx
On some installation you should also look at IIS Manager settings for the rpc virtual directory. The process is similar to that of setting up the exchange virtual directory for Outlook Web Access.
Exchange Server Registry Changes
Single Server Configuration
Exchange Server is also the domain controller
The domain controller needs to be a Global Catalog Server, but only requires one entry.
That key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
Type REG_MULTI_SZ
Name: NSPI Interface protocol sequences
Value: ncacn_http:6004
or you can download this file rpc-http-dc.txt and change it to rpc-http-dc.reg
Than add this key:
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy
Key:ValidPorts
Key:
server = domain controller/exchange server
domain.local = internal domain name
mail.external.com - external domain name - then change "domain.local" to match your domain.
or you can download this file rpc-proxy.txt edit the file to match you exchange server and change it to rpc-porxy.reg
You need reboot the server
Front-End / Back-end Server Configuration
Where there are two Exchange servers and a separate domain controller.Key:
server-fe = Front-end Exchange Server
server-be = Back-end Exchange Server
server-dc = Domain Controller with Global Catalog
domain.local = Internal domain name
mail.external.com = External certificate/domain name
or you can download this file rpc-http-porxy-fornt.txt. edit the file to match you exchange server and change it to rpc-porxy-front.reg
Testing the port configuration
do a telnet chack to port 6001, 6002, 6004
telnet localhost 6001
telnet localhost 6002
telnet localhost 6004
if the telnet is not connecting to one of this port check the reg key again,
the most populer problem is with the port 6004 so run this rpc-http-dc.txt (change the name to rpc-http-dc.reg) and reboot the server
Test the System from Outside using Microsoft's Test Site
Microsoft have created a test site for Exchange features. use a test account with it.
https://testexchangeconnectivity.com
Create a Microsoft Office Outlook 2003 Profile for your users to use with RPC over HTTPS
Next, we must configure the Microsoft Outlook 2003 Profile to use RPC over HTTPS.
Navigate to the Control Panel in your Windows XP Professional Workstation and click the Mail icon. Add a new Mail profile or modify an existing Profile. Navigate to the Connection Tab and check the Checkbox Connect to my Exchange mailbox using HTTP and then click the Exchange Proxy Settings Button.
Figure 7: Enable RPC Proxy Settings
Enter your Server Information, similar to Figure 8.
Figure 8: Exchange Proxy Settings
Test the Connection
After enabling the RPC Proxy settings, your Outlook connection to the Exchange Server should be established successfully. The question is now: How to determine that it is an RPC over HTTPS connection?
The answer is simple. Right click the Outlook icon in the taskbar while you are holding the CTRL Key. The Context menu opens and now you have the option to see the Exchange Server Connection Status.
Figure 9: Test the RPC over HTTPS connection
Congratulations! You have successfully enabled your Exchange Server 2003 / Microsoft Outlook 2003 environment to use the RPC over HTTPS feature.