Access your Pro+ Content below.
Three methods to repair OWA
This article is part of the Exchange Insider issue of April 2012, Vol. 13
Outlook Web Access and Outlook Web App 2010 are both low-maintenance Exchange Server components. Aside from applying the occasional update, you don’t need to do much to keep OWA running. But when these components fail, it has a major impact on end users. Here are three techniques you can use to get OWA back up and running. 1. Start with OWA basics If one of your OWA servers malfunctions, the first thing you should do is check the server clock. If the clock falls out of sync with your domain controllers, Kerberos authentication will fail. This leads to OWA and ActiveSync problems. After you’ve checked the server’s clock, verify that the domain name system (DNS) name resolution works properly. I’ve traced many OWA problems to incorrect entries on internal DNS servers. 2. Client access server: To rebuild or not to rebuild? Almost all the important Exchange configuration information is stored in Active Directory, not on Exchange servers. This makes things easier when you need to rebuild a malfunctioning Exchange server. In fact, you...
Access this PRO+ Content for Free!
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Features in this issue
A move to the cloud eliminates certain administrative chores. One task you must still handle is records management. Read about Exchange Online retention policies and the PowerShell you’ll need here.
Admins have several options to repair OWA. The trick is choosing the technique that has the least amount of impact on your OWA user base. Consider these three fixes.