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
2 MIN READ
Outlook 2007 can now use DNS SRV records to find the location of the Exchange Autodiscover Service
Elan,
I did not do the Get-ExchangeCertificate and Enable-ExchangeCertificate commands. But I did the "old" way on IIS, by importing the certificate (.pfx). Are the two commands supposed to make any difference from the standard IIS certificate import?
I just ran the two commands above on tha CAS server anyway. And I confirmed the AutodiscoverURI value is set correctly. But I did not notice any difference they made. I even rebooted the CAS server, as well as the Outlook client, but still got the same security alert at the same spot. Please note that this security alert is not the same as what I got when those URLs were not set correctly. It is about not trusting the self-assigned cert on that CAS server. Is there anything else I should look into?
Thanks for your time!
Adam
I did not do the Get-ExchangeCertificate and Enable-ExchangeCertificate commands. But I did the "old" way on IIS, by importing the certificate (.pfx). Are the two commands supposed to make any difference from the standard IIS certificate import?
I just ran the two commands above on tha CAS server anyway. And I confirmed the AutodiscoverURI value is set correctly. But I did not notice any difference they made. I even rebooted the CAS server, as well as the Outlook client, but still got the same security alert at the same spot. Please note that this security alert is not the same as what I got when those URLs were not set correctly. It is about not trusting the self-assigned cert on that CAS server. Is there anything else I should look into?
Thanks for your time!
Adam