Continuing the blogcast series on infrastructure essentials.
We now move Outlook Web Access back to HTTPS, and we correct a naming error on the Network Listener "FBA LocalHost 443" in the last part (it's actually listening and remains listening on port 80). After having ripped things apart over the last few parts to this series, we piece things back together by updating the publishing rule "ExternalBasic-LocalHost (OWA)" for redirection of https://mail.contoso.com to https://mail.contoso.com/exchange
Only two more parts to go for a fully configured ISA Server publishing Exchange OWA and RPC/HTTP. Stay tuned.
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 work22. RPC/HTTP: Bounce OWA through localhost
ISA 2004 SP2 will no longer allow FBA listeners to use HTTP... meaning you'll have to use SSL for LocalHostFBA listener as well.