Loendar
asked on
SSL Certificate error - Exchange 2010
After our initial migration from 2003 to 2010 everything had been running swimmingly. The Exchange 2010 server automatically made a default SSL certificate that it was using for everything but for obvious reasons external access to OWA didn't count as secure.
I purchased the appropriate SSL certificate for our OWA server and applied it via the Exchange 2010 management console. Unfortunately during that process it decided that it would also apply itself to SMTP in addition to the OWA required services. So *now* when an internal user opens Outlook they are immediately prompted that the SSL certificate is showing the incorrect name (twice). You can accept it each time and move on, but I need to get back to the point where the internal certificate is assumed valid for SMTP and the purchased one is still used for external connections (which are working atm).
I purchased the appropriate SSL certificate for our OWA server and applied it via the Exchange 2010 management console. Unfortunately during that process it decided that it would also apply itself to SMTP in addition to the OWA required services. So *now* when an internal user opens Outlook they are immediately prompted that the SSL certificate is showing the incorrect name (twice). You can accept it each time and move on, but I need to get back to the point where the internal certificate is assumed valid for SMTP and the purchased one is still used for external connections (which are working atm).
ASKER
I've done those things and they show accurately. In fact, I exported the purchased OWA certificate and removed it, issued the New-ExchangeCertificate command since the internal certificate that was there originally didn't work and restarted both the 2003 and 2010 servers (seems they don't like to talk over SMTP after these are changed without a restart).
At that point the Outlook clients were happy again presumably using the new SSL cert. As soon as I re-imported the OWA one (even though SMTP wasn't checked) it was back to square one only now I had TWO self-signed certificates. It really is pretty odd.
At that point the Outlook clients were happy again presumably using the new SSL cert. As soon as I re-imported the OWA one (even though SMTP wasn't checked) it was back to square one only now I had TWO self-signed certificates. It really is pretty odd.
Did you included Internal host name in certificate ?
& does it give any error when accessing from OWA?
& does it give any error when accessing from OWA?
ASKER
OWA is working flawlessly with the external certificate in place.
The issue is that the internal signed one previously was the server name and it was happy with that... now it is trying to use the certificate for the external name which doesn't match. Really I just need to figure out how to get it to stop using the SSL certificate for SMTP.
The issue is that the internal signed one previously was the server name and it was happy with that... now it is trying to use the certificate for the external name which doesn't match. Really I just need to figure out how to get it to stop using the SSL certificate for SMTP.
You can remove service association by going to Server configuration >exchange certificates>select self signed certificate & assign services to certificate
ASKER
I shall give that a shot - thanks!
Once you assign services to self signed you will be able to remove it from other certificate.
ASKER
You are correct - it did allow me to remove the old one but sadly didn't stop the error message from happening when starting Outlook.
Really I would prefer to have SMTP not validated at all internally but it seems they force it.
Really I would prefer to have SMTP not validated at all internally but it seems they force it.
If you have included your internal host name(FQDN -like mailserver.windowsdns.inte
like your certificate should include as example
mail.externalhost.com
mail.internalhost.com
mailserverhostname(FQDN)
that will prevent error from coming.
like your certificate should include as example
mail.externalhost.com
mail.internalhost.com
mailserverhostname(FQDN)
that will prevent error from coming.
ASKER
Sadly - I did not. It was only meant to apply to external names and I didn't think that it would try to apply itself internally as well. In fact, since it was meant just for OWA and OMA it never occurred to me that it would set itself up on the SMTP port.
When you run outlook internally it will try to look for the FQDN host name entry in certificate. if it did not find then it will give certificate error as you are receiving.
ASKER
Well - i have tried to get the certificate reissued to include the FQDN used for our internal email server in the hopes that it would stop the error message. Sadly, since we don't own the public version of the domain name they seem unlikely to provide it and I'm back to square one.
Outlook is looking at the external SSL certificate and refusing to acknowledge the internal one for SMTP.
Outlook is looking at the external SSL certificate and refusing to acknowledge the internal one for SMTP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1. Certificate shows correct status on EMC
2. Services assigned correctly to Certificate
3. check certificate by get-certificate
also check this link if it helps
http://technet.microsoft.com/en-us/library/aa995942.aspx