Continuing the blogcast series on infrastructure essentials.
The final part to the RPC/HTTPS series shows you how to alter the configuration we have such that Outlook 2003 can move seamlessly between external and internal connectivity through the use of integrated authentication. To do this, we need to change both the ISA server and the Exchange server. The overall end user experience, as you will see, is far better.
So over the Christmas break, I'll get round to recording a few more parts to the series, including VPN connectivity.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 localhost23. RPC/HTTP: OWA Back to HTTPS24. RPC/HTTP: RPC Publication
Nice blogcast with a feature that is not very well known by many - notice that if you have problems with Outlook still popping up with requests for username/password it might be due to the LM Compatibility Level settings on the client as per se