RPC over HTTPS
This is our section on RPC over HTTPS, the feature of Exchange 2003 and Outlook 2003 that allows a connection to an Exchange server, over the internet, without a VPN.
The configuration pages on this site come from a working Exchange 2003 SP2 environment and are based on our own work.
Despite other documentation may read, you do NOT need to have a frontend / backend scenario to use this feature, nor do you need to have an ISA server. It can be deployed with a single Exchange server. You must be on Exchange 2003 on Windows 2003 and you must have at least one Windows 2003 GC/DC.
Initial Setup
Server
Server configuration instructions, includes registry entries for a single Exchange server.
This server setup section is NOT required to deploy Outlook Anywhere on Exchange 2007/2010. With Exchange 2007/2010 you do not have to make any registry changes. Exchange 2010 Instructions.
Client - On Domain
Configuring Outlook to connect to the server using RPC/HTTPS or Outlook Anywhere.
Client - Off Domain
How to configure an Outlook client that isn't connected to your domain or network
Troubleshooting and Verifying functionality
Diagnostics
How to diagnose that it is working correctly, and where the problem may be.
Common Questions and Solutions
Some of the more common questions when setting up this feature
Tips on Successful Implementation - based on our experience of implementing this feature we have collected together some of the techniques to ensure a successful implementation.
External Links
Microsoft Deployment Scenario's White Paper.
KB Articles:
RPC/HTTPS on a single server: http://support.microsoft.com/kb/833401