authentication and encryption of For PEAP authentication: a traffic. certificate is required on each RADIUS server. S/MIME S/MIME is used as a standard For S/MIME signing: for public key encryption and certificate on the sender. signing of email encapsulated For S/MIME encryption: in MIME. S/MIME is natively certificate on the recipient. supported in Microsoft Office For SSL encryption: Outlook® and Outlook Web certificate on each mail Access in Exchange Server server. with the S/MIME control. SSL can be used to encrypt email traffic as well as to validate the identity of the email server. Windows Mobile Windows Mobile devices use For (optional) HTTPS/SSL devices certificates for encryption of encryption and authentication traffic and optionally for of the server: certificate on authentication of the Exchange the server. ActiveSync feature. To optionally authenticate the For more information about the client, a certificate on each certificate requirements for client that may connect. Windows Mobile, see an Authentication “Choosing Method for Your Exchange ActiveSync Server” at . Exchange Computers running Exchange For SMTP encryption and Server 2007 Server use certificates for authentication: certificates on authentication and encryption of the Hub Transport servers traffic between servers and and on Edge Transport between servers and clients. servers. For more information on the For EdgeSync LDAP certificate requirements for encryption: certificate on the Exchange Server, see Edge Transport server. Use in Exchange “Certificate For POP3 and IMAP Server” at . authentication: certificate on the Client Access server. For Unified Messaging: certificate on the Hub Transport server, the UM IP Gateway and Communications Server 2007. For Autodiscover: certificate on the Client Access server. For Client Access HTTP clients: certificate on the Client Access server.
authentication and encryption of traffic. For PEAP authentication: a certificate is required on each RADIUS server. S/MIME S/MIME is used as a standard for public key encryption and signing of email encapsulated in MIME. S/MIME is natively supported in Microsoft Office Outlook® and Outlook Web Access in Exchange Server with the S/MIME control. SSL can be used to encrypt email traffic as well as to validate the identity of the email server. For S/MIME signing: certificate on the sender. For S/MIME encryption: certificate on the recipient. For SSL encryption: certificate on each mail server. Windows Mobile devices Windows Mobile devices use certificates for encryption of traffic and optionally for authentication of the Exchange ActiveSync feature. For more information about the certificate requirements for Windows Mobile, see “Choosing an Authentication Method for Your Exchange ActiveSync Server” at . For (optional) HTTPS/SSL encryption and authentication of the server: certificate on the server. To optionally authenticate the client, a certificate on each client that may connect. Exchange Server 2007 Computers running Exchange Server use certificates for authentication and encryption of traffic between servers and between servers and clients. For more information on the certificate requirements for Exchange Server, see “Certificate Use in Exchange Server” at . For SMTP encryption and authentication: certificates on the Hub Transport servers and on Edge Transport servers. For EdgeSync LDAP encryption: certificate on the Edge Transport server. For POP3 and IMAP authentication: certificate on the Client Access server. For Unified Messaging: certificate on the Hub Transport server, the UM IP Gateway and Communications Server 2007. For Autodiscover: certificate on the Client Access server. For Client Access HTTP clients: certificate on the Client Access server.