Top 5 Outlook Web Access (OWA) tips of 2008

Check out the Top 10 Outlook and OWA tips of 2007.

Submit your own OWA tip today!
Based on your views, here are our top five Outlook Web Access (OWA) tips of 2008. Some topics that piqued your interest in 2008 ranged from how to customize your OWA authentication logon, repairing damaged virtual directories and creating a secure OWA redirect page.

This was first published in January 2009

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top
    #1    How to customize OWA authentication logon in Exchange Server 2003
    In Exchange Server 2003, Outlook Web Access (OWA) authentication requires, by default, a domain name and username to log on. Learn to customize the OWA logon and avoid this hassle.
    #2    Fix OWA message size limit issue after upgrading to Exchange 2007 SP1
    After an Exchange Server 2007 SP1 upgrade, OWA can no longer send large attachments. Discover how to troubleshoot this OWA issue in Exchange Server 2007 SP1.
    #3    OWA won't load after applying Exchange 2007 SP1 security patch
    Microsoft's security patch, Update Rollup 2 for Exchange Server 2007 SP1, can break the Client Access server. When this occurs, logging into OWA returns a blank screen. Find out how to fix this OWA issue and also how to avoid future patching problems.
    #4    Repairing damaged OWA virtual directories in Exchange Server 2003
    Virtual directory corruption in Exchange Server 2003 can prevent Outlook Web Access (OWA) from displaying icons properly. Repair these corrupt Exchange directories and keep OWA from displaying icons as red Xs or showing "Loading" messages.
    #5    Create a secure Microsoft Outlook Web Access (OWA) redirect page
    Incorrectly typing the URL for your Microsoft Outlook Web Access (OWA) page will result in an error message. Because users may mistakenly type HTTP instead of HTTPS to access OWA, you can easily create an OWA redirect page that doesn't sacrifice secure sockets layer (SSL) security.