Hi,

We have a Exchange 2013 server hosted on our own premises. 

I have just had to renew the SSL certificate, with the new ruling I can't have the ???.local domain on the certificate.

My users now get the following error when they start Outlook.

There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site servername.localdomain.local.

Outlook is unable to connect to the proxy server. Error Code 10

Any advice with this would be greatly appreciated.

Regards

Dan

Basically, you need to tune various Exchange configurations to match the names in the new cert. I explained in detail here,

http://exchange929.blogspot.com/2015/08/outlook-security-alert-aka-cetificate.html

Basically, you need to tune various Exchange configurations to match the names in the new cert. I explained in detail here,

http://exchange929.blogspot.com/2015/08/outlook-security-alert-aka-cetificate.html

• Proposed as answer by Niko.ChengMicrosoft contingent staff, Moderator 5 hours 14 minutes ago

Basically, you need to tune various Exchange configurations to match the names in the new cert. I explained in detail here,

http://exchange929.blogspot.com/2015/08/outlook-security-alert-aka-cetificate.html

• Proposed as answer by Niko.ChengMicrosoft contingent staff, Moderator Friday, August 07, 2015 2:16 AM

Basically, you need to tune various Exchange configurations to match the names in the new cert. I explained in detail here,

http://exchange929.blogspot.com/2015/08/outlook-security-alert-aka-cetificate.html

• Proposed as answer by Niko.ChengMicrosoft contingent staff, Moderator Friday, August 07, 2015 2:16 AM

Hi Dan,

Except above suggestion, you can also refer to the following KB article, it may help you to resolve the issue:

https://support.microsoft.com/en-us/kb/2772058

Best regards,

Basically, you need to tune various Exchange configurations to match the names in the new cert. I explained in detail here,

http://exchange929.blogspot.com/2015/08/outlook-security-alert-aka-cetificate.html

Hi,

So I ran the command outlined in the document and this is what I got

[PS] C:\Windows\system32>Get-ClientAccessServer | fl Name,AutodiscoverServiceInternalUri


Name                           : SERVERname
AutoDiscoverServiceInternalUri : https://mail.mydomainname.com/autodiscover/autodiscover.xml

My SSL contains mail.mydomainname.com

With this in mind I would have thought this is correct?

I only have the problem locally when seemingly the dns resolution still looks at the internal server name.

Am I missing something?

That's not all. Pleae also have a look at the other part of the blog post.