28 October 2005

Part 19: Infrastructure essentials Blogcast - RPC/HTTP for Outlook & Exchange - Completing internal config

Continuing the blogcast series on infrastructure essentials.

This fourth part of configuring RPC over HTTP for Outlook 2003 moves us on to ensuring that RPC/HTTP works internally from our Outlook 2003 client to our Exchange 2003 Server. First though, we correct a typo in the registry settings from the previous blogcast part (sorry!). One thing that is critical is to correctly configure our Outlook Profile for RPC/HTTP connectivity. We walk through the settings and change them, take a look at the "/rpcdiag" switch when starting outlook and end up with Outlook talking to our Exchange server through HTTPS internally.

Next week, we'll start tackling the ISA Server configuration to get RPC/HTTPS available from the Internet.

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

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

No Comments

Leave a Comment

Comment Policy: No HTML allowed. URIs and line breaks are converted automatically. Your e–mail address will not show up on any public page.

(required) 
(optional)
(required) 
Page view tracker