Update 10/4/2007: Since this post has been published, we've 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
I run into this problem after applying a cert from godaddy to my CAS box. I run the cmdlet below and all is well from what I can tell. Both OWA and Outlook 2007 clients connect with no certificate errors.
if you are using a commercial certificate from Verisign or Godaddy to work around it you can use the following CMDLET to update the SCP inside of the AD: Set-WebServicesVirtualDirectory -Identity "EWS*" -ExternalUrl "Https://mail.synergyps.com/EWS/Exchange.asmx"
-InternalUrl "Https:// mail.synergyps.com/EWS/Exchange.asmx".- the previous command will update all of the services (OAB,Free/Busy,OOF,GAL) address, but if you are interested in updating the Autodiscovery SCP only you can use the following CMDLET:
Set-ClientAccessServer -Identity CASserver1 -AutoDiscoverServiceInternalUri https://mail.synergyps.com
https://mail.synergyps.com this will allow you to use a commercial certificate along with your secure deployment of exchange 2007 and avoid the common errors most of the customers complained from when using AutoDiscovery service
read more here
http://busbar.maktoobblog.com/?post=271192