PRO+ Premium Content/Exchange Insider

Thank you for joining!
Access your Pro+ Content below.
November 2010, Vol. 7

Step up your Outlook Web App setup

Outlook Web App is enabled by default on an Exchange 2010 client access server, but that doesn’t mean it’s going to work optimally. You’ll need to reconfigure OWA after installing the CAS role to get the application running smoothly and securely. When you install the client access server role, Exchange requires SSL encryption for OWA. That SSL encryption is linked to a self-signed certificate, which temporarily secures HTTP communications with the CAS. Unlike a traditional SSL certificate, a self-signed certificate doesn’t provide proof of the CAS’s identity. Furthermore, client computers don’t trust self-signed certificates, and they shouldn’t. Consequently, users will receive certificate errors when they try to access OWA (Figure 1). Figure 1. Users will receive certificate errors if OWA relies on the built-in self-signed certificate. To resolve this, you need to acquire an X.509 certificate from a trusted certificate authority (CA). You can either use a commercial CA or you can generate the certificate in-house. I recommend ...

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.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

Features in this issue