Access your Pro+ Content below.
Step up your Outlook Web App setup
This article is part of the November 2010, Vol. 7 issue of Exchange Insider
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 ...
Features in this issue
Virtualizing Exchange 2010 servers is a smart move, and the steps involved are fairly simple. The actual virtualization process begins long before you create a VM.
When Outlook Web App’s default settings just won’t do, it’s time to tweak. Certain configuration changes will help OWA run more efficiently and securely.
After you've installed Exchange Server for a client, it's time to write the installation documentation. Providing consistent and easy-to-understand documentation is vital for both Exchange administrators and users. These three principles of good documentation writing can help.