Continuing the blogcast series on infrastructure essentials.
To make the next steps clearer, here's a picture of what we're trying to achieve in combining Forms Based Authentication with RPC/HTTP, and the routes through which traffic will flow. Hopefully a picture speaks a thousand words - the blogcast goes through configuring ISA to bounce OWA traffic through our Localhost listener. As you watch, you'll notice that no-one is infallible (and especially count myself in that list), but it was only a minor mistake :)
Click here to view.
Series Index:0. Network configuration and series background.1. Getting started2. ISA Server configuration to allow basic web browsing capability3. ISA Firewall Client basic configuration4. ISA Firewall Client auto-detection through WPAD configuration5. Configuring an Exchange mailbox and Outlook profile6. Fixing 0x8004010F on Outlook send/receive7. Installing our first Certificate Authority8. Publishing OWA through ISA using Forms Based Authentication9. OWA /exchange redirection10. OWA nearly goes SSL - we have a certificate11. OWA is available over SSL/HTTPS12. Sending external email - Configuring outbound SMTP13. Mail retrieval through POP3 polling14. Preparations for Email retrieval through SMTP Transfer15. Completing Email retrieval through SMTP Transfer16. RPC/HTTP: Overview and installing RPC Proxy component17. RPC/HTTP: IIS Config and a bit on certificates18. RPC/HTTP: Exchange IIS Config completion19. RPC/HTTP: Working from internal network20. RPC/HTTP: Revisiting our ISA rules21. RPC/HTTP: Outlook working externally. OWA still requires more work
Can i place the RPC Proxy Service on a back-end Exchange Cluster Machine?
For multi-server Exchange RPC deployment scenarios, take a look on TechNet for more information: http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/ex2k3rpc.mspx. These scenarios can be far more complex than the relatively simple example I'm walking through here.