Access your Pro+ Content below.
Obtaining and verifying SSL certificates in Exchange Server
This article is part of the Exchange Insider issue of April 2009, Vol. 1
Many of the security features that are built into Exchange Server rely on SSL. Understanding and implementing SSL concepts is required for proper Exchange infrastructure management. SSL certificates are not new. When we buy something online, we frequently see the padlock icon in our browsers. This indicates that we're conducting our transactions over a secure, or SSL-enabled, connection that encrypts our data. Much of the functionality and many of the security features built into Microsoft Exchange Server 2003 and Exchange Server 2007 rely on SSL. For example, Outlook Web Access (OWA), Outlook Anywhere, mobile devices and Macintosh computers are already configured to use SSL for basic security and functionality. Therefore, having knowledge of SSL concepts as well as the method to actually implement SSL has become a requirement for properly managing your infrastructure. A trusted certificate is one that a recognized certification authority (CA), such as Verisign, Thawte, GoDaddy and others, has created. Windows Server includes ...
Access this PRO+ Content for Free!
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Features in this issue
A successful Exchange Server email-archiving strategy requires planning, including backup and storage methods as well as how long to retain email messages.
Many security features in Exchange Server rely on SSL. Obtaining trusted certificates can tighten security and boost performance for SSL-based applications, including OWA and Exchange mobile devices.
Get an overview of Exchange Server 2007 pre-migration requirements, including running on 64-bit CPU and native mode, as well as some legacy server issues