Continuing the blogcast series on infrastructure essentials.
Yesterday, we got Outlook Web Access available on the Internet (albeit still using http rather than https - later this week we'll solve that). Our users are currently accessing Outlook Web Access using the URL http://mail.contoso.com/exchange. Users being users (bless them), like to remember as little as possible and call the help-desk, office technicial guru or simply blame everything but themselves for not being able to remember to tack on "/exchange". Well, the good news is that there's a few tricks up our sleeve to make sure users only have to remember http://mail.contoso.com instead. In this blogcast, I look at a home-brewed way using a simple script to force the redirection. It does work, but I conclude due to the "supportability" issue, it is not ideal. Good news is though that I have since found an even better way of doing it, thanks to an article Tom Schinders excellent site, isaserver.org.
This is the script I used in this blogcast is:
<%@ language=VBScript %><%response.redirect "/exchange"%>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 Authentication