In a series of Screencasts we will cover the different scenarios for configuring RPC over HTTPS for Exchange Server 2003 and Outlook Anywhere for Exchange Server 2007
In the following Step-by-Step Screencast we will demonstrate one of the most popular scenarios, where Exchange Server(s) and Domain Controller(s)/Global Catalog(s) are running on separate machines. There isn’t a front-end Exchange server in this Scenario and again, it is important to note that Exchange Server 2003 is NOT running on a Domain Controller in this demonstration. As you can see this requires specific configuration changes on the Global Catalog(s) which Exchange Server 2003 is using.
Here are the prerequisites for this Scenario :
– Exchange Server 2003 with SP1 or higher
– Windows Server 2003 or Windows Server 2008 on the Global Catalog(s) which Exchange Server 2003 is using
– Outlook 2003/2007 running on Windows XP with SP2 or higher, or Windows Vista
To keep things simple, we will dedicate a separate Screencast, covering the different client configuration scenarios – Windows XP, Windows Vista, Outlook 2003, Outlook 2007, clients located outside (at a remote location), clients located on the local network (configuring Split DNS) and last but not less important – using self-issued SSL certificate with RPC over HTTPS.
In this Screencast, after we configure the Domain Controller/Global catalog and the Exchange Server 2003 we will show you how to configure and test RPC over HTTPS connection on a client at a remote location, running Windows XP, SP3 and Outlook 2007.
For your convenience you can download the text file, with the registry settings used in the demo, and the rpccfg.exe utility.
