When installing an Exchange 2013 Edge Transport server a self-signed certificate is created and configure for use with the SMTP Transport server. The self-signed certificate has the NetBIOS hostname as the Common Name and the FQDN in the Subject Alternate Names field.
You can view this self-signed certificate using the Certificate MMC snap-in:
Continue reading Exchange 2013 Edge Transport Server and SSL Certificates
A Lync 2013 Edge server is using external, 3rd party certificates for authentication and encryption of data for federation purposes and external clients connecting to the Lync 2013 environment. I’m using Digicert certificates for this since these work fine in almost all situations.
So I got a message from Digicert to renew my certificate, which I did. Renewed the certificate, same Common Name (CN=access.exchangelabs.nl) and the same Subject Alternative Names entries. The order of the SAN entries was different and so was the Friendly Name of the certificate but this should not cause any problem.
Continue reading Polycom CX600 fail to login after Certificate renewal on Lync 2013 Edge Server
Autodiscover is a standard feature in Exchange Server 2007 and higher that’s being used by Outlook 2007 and higher. Looking at the number of questions I get regarding autodiscover I’ve written a number of blogposts that will look into Autodiscover in depth:
In Part I I’ve explained how domain joined clients work with autodiscover information that’s stored in Active Directory. In Part II I’ve explained how the same (domain joined) client behaves on an external network like the Internet.
Both posts work with the self-signed certificate, but it’s much better (and recommended!) to use a 3rd party certificate or a certificate of an internal PKI environment. Continue reading Autodiscover in Exchange part III