共用方式為

Part 25: Infrastructure essentials Blogcast - RPC/HTTP for Outlook & Exchange - Integrated Auth

  • 發行項

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 started
2. ISA Server configuration to allow basic web browsing capability
3. ISA Firewall Client basic configuration
4. ISA Firewall Client auto-detection through WPAD configuration
5. Configuring an Exchange mailbox and Outlook profile
6. Fixing 0x8004010F on Outlook send/receive
7. Installing our first Certificate Authority
8. Publishing OWA through ISA using Forms Based Authentication
9. OWA /exchange redirection
10. OWA nearly goes SSL - we have a certificate
11. OWA is available over SSL/HTTPS
12. Sending external email - Configuring outbound SMTP
13. Mail retrieval through POP3 polling
14. Preparations for Email retrieval through SMTP Transfer
15. Completing Email retrieval through SMTP Transfer
16. RPC/HTTP: Overview and installing RPC Proxy component
17. RPC/HTTP: IIS Config and a bit on certificates
18. RPC/HTTP: Exchange IIS Config completion
19. RPC/HTTP: Working from internal network
20. RPC/HTTP: Revisiting our ISA rules
21. RPC/HTTP: Outlook working externally. OWA still requires more work
22. RPC/HTTP: Bounce OWA through localhost
23. RPC/HTTP: OWA Back to HTTPS
24. RPC/HTTP: RPC Publication

Comments

  • Anonymous
    December 19, 2005
    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 sehttp://support.microsoft.com/default.aspx?scid=kb;en-us;820281