We have already demonstrated the installation and initial configuration of Exchange 2013 Multirole (CAS + MBX) server. The next logical step is configuring the Exchange URL and installing a trusted Multiple Domain certificate.

By default, Exchange setup generates and assigns to Exchange services a self-signed multiple domain certificate, which has five years validity and contains just the internal Exchange short (NetBIOS) and AD Fully Qualified Domain Name (FQDN). As you can expect, this certificate is not trusted by the local and remote clients. In addition, it doesn’t include the Exchange server public and autodicover names which makes it unusable for remote Outlook Anywhere clients. The self-signed certificate is a temporary solution and needs to be replaced as soon as possible. When deploying a test Exchange 2013 lab, you might consider generating a new self-signed certificate with the Subject Alternative Names (SAN) that you need or requesting a Multiple Domain Certificate from an Enterprise Certificate Authority. For a production environment, the recommended approach is implementing a trusted commercial certificate.

In this Screencast, we demonstrate how to configure the Exchange 2013 URL and how to install a GoDaddy UCC. For your convenience, we have published the text file with the commands that we are using in the Screencast here .

Step 1 We start with a discussion of the new baseline requirements for the issuance and management of publicly-trusted certificates. Then, we proceed with planning the subject alternative names that need to be included in the new certificate.

Step 2 In this step, we configure Exchange 2013 URL and create PinPoint DNS zones for the public names that will be included in the new multiple domain certificate/UCC.

Step 3 In the last step, we request and install a new GoDaddy multiple domain certificate in Exchange 2013.