Quantcast
Channel: Exchange Server 2013 - Administration, Monitoring, and Performance 论坛
Viewing all articles
Browse latest Browse all 3457

New SSL Certificate - Reconfiguring Exchange to use FQDN - Exchange 2010 SP3

$
0
0

We are using Exchange 2010 SP3.

Our SSL certificate in Exchange is approaching expiration.  I used the "New Exchange Certificate..." wizard to create a new certificate request.  In this process there are certain internal host names added as Subject Alternative Names, including the internal client access server name.  

While submitting the CSR to godaddy that is when I learned it is no longer possible to include internal domain names on a public SSL certificate.   (More info: GoDaddy's explanation of the changes

I have found various websites which provide tools and instructions to reconfigure Exchange Server to use your external fully qualified domain name.  (Example of GoDaddy's instructions, and Example of Digicert's instructions)

This process includes the following:  

1. Changing the Autodiscover URL

2. Changing the InternalURL attribute of the EWS

3. Changing the InternalURL attirbute for web-based offline address book distribution

My question is in regards to internal Microsoft Outlook Client mapi users.  When I look at the account settings in Outlook the server is the internal host name of the client access server.  

Since the internal host name of the client access server will not be in the SSL certificate will Outlook break?

Do I need to manually change this for all internal mapi clients?  Or will autodiscover take care of it?  The self signed certificate for the internal name of the client access server is still valid, is that all the internal clients need

Thanks anyone.


Viewing all articles
Browse latest Browse all 3457

Trending Articles