usslindstrom
asked on
Certificate Warning Outlook 2007 --> Exchange 2007
Experts,
I've read many forums and TechNet posts on this topic, but I'm having some issues trying to correct / resolve my issue.
First, let me go over my layout.
I have 2 Exchange Servers, 1 with all the roles, and another that's just a CAS (front end web-server).
The Outlook clients are warning that they're trying to reach mail.domainname.com and that doesn't match what's on the certificate (which is servername.domainname.com) .
I know this has 100% to do with the autodiscover stuff that the clients are trying to resolve. For DNS, I have a CNAME for "autodiscover" pointing to servername.domainname.com. - As well as mail.domainname.com is a CNAME pointint to the same server.
In the code block below, here is some output.
Any ideas on how to make the warning go away?
I've read many forums and TechNet posts on this topic, but I'm having some issues trying to correct / resolve my issue.
First, let me go over my layout.
I have 2 Exchange Servers, 1 with all the roles, and another that's just a CAS (front end web-server).
The Outlook clients are warning that they're trying to reach mail.domainname.com and that doesn't match what's on the certificate (which is servername.domainname.com)
I know this has 100% to do with the autodiscover stuff that the clients are trying to resolve. For DNS, I have a CNAME for "autodiscover" pointing to servername.domainname.com.
In the code block below, here is some output.
Any ideas on how to make the warning go away?
Get-ExchangeCertificate
Thumbprint Services Subject
---------- -------- -------
***** IPUWS CN=servername.domainname.com
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Thanks for the update and points ,Have a great day ,God Bless you.
ASKER
Viralrathod, that link you send was great.
I changed the https://url on the autodiscover and other ones using the exchange shell to https://servername.domainname.com and it looks like it resolved my issue.
I swore I saw that link before, which is why my setup was mail.domainname.com - but that's the error my clients were getting, on that exact name. I figured after reading through your post again, that I should at least try it with the way it's setup now.
Seems to be OK.
Thanks.