Link to home
Start Free TrialLog in
Avatar of Charlie Fraser
Charlie Fraser

asked on

Added 2 2016 Exchange Servers - Certificate Warning.

I have 1 on Prem Exchange 2013 servers and I'm trying to migrate to Exchange 2016. I moved my mailbox to one of the new servers and now I get a certificate warning only when I connect to exchange using Outlook connected to the corporate network. All of the internal uri's are pointing to the internet fqdn. The SAN cert is complaining that the local exchange server isn't in the SAN cert which it isn't. This works no problem for the Exchange 2013 server. Is there another setting I'm missing? Thanks in advance.
Avatar of Charlie Fraser
Charlie Fraser

ASKER

I changed the outlookanywhere setting for the new server where my mailbox is on and I still get the certificate error.
Avatar of Amit
You need to apply certificate on your new Exchange 2016 server as well. You can export from your Exchange 2013 server and import on your Exchange 2016, assign the services, what you have assigned in Exchange 2013. And you should be good to go.
I installed the SSL cert from the 2013 server before I did anything else. My problem is that when I connect with Outlook on the corporate network it's telling me that the AD fqdn of the server ie: Exchangeserver2.ADdomain.inetdomain.com  The SAN cert has mail.inetdomain.com, autodiscover.inetdomain.com. and inetdomain.com. Again, this certificate is working fine with the 2013 server it's just when I connect via outlook on the corporate network.
Did you check the bindings in IIS to ensure the new certificate is used?
Yes the default site is using the SAN cert "mail.mydomain.com".
ASKER CERTIFIED SOLUTION
Avatar of Charlie Fraser
Charlie Fraser

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial