EDIT 10/4/2007: Since this post has been published, we have updated the Exchange 2007 Autodiscover Service whitepaper to include this information. Please consult the whitepaper for most up-to-date ...
Updated Jul 01, 2019
Version 2.0
Blog Post
Before I go out and by another certificate I want to make sure that this is going to work.
I setup Exchange 2007 on my internal network. I setup a route though my firewall for OWA and Activesync, I created a FQDN of mobile.mydomain.com. I bought a certificate for mobile.mydomain.com. External access works well.
However, internal users connecting to the new server with Outlook 2007 get prompted twice because the certificate doesn't match the internal server which is ppgexg001.mydomain.local.
According to what I have read here, if I create a new host record for autodiscover.mydomain.com and buy a 2nd certificate for autodiscover.mydomain.com and apply it using the instructions here, the internal users will no longer be bothered with certificate errors?
Can you confirm this please.
Paul S
I setup Exchange 2007 on my internal network. I setup a route though my firewall for OWA and Activesync, I created a FQDN of mobile.mydomain.com. I bought a certificate for mobile.mydomain.com. External access works well.
However, internal users connecting to the new server with Outlook 2007 get prompted twice because the certificate doesn't match the internal server which is ppgexg001.mydomain.local.
According to what I have read here, if I create a new host record for autodiscover.mydomain.com and buy a 2nd certificate for autodiscover.mydomain.com and apply it using the instructions here, the internal users will no longer be bothered with certificate errors?
Can you confirm this please.
Paul S