I have two client access servers with Outlook Anywhere enabled and one clustered mailbox server (all have SP1 loaded). When I try to setup a test profile on my workstation using Outlook 2007 SP1, I get "An encrypted connection to your mail server is not available. Click Next to attempt using an unencrypted connection". This eventually fails even if I try using an unencrypted connection. I can setup a test profile successfully if I use my own Domain Admin account. No other accounts from any other hosted company work.
Posts: 62
Joined: 14.Apr.2008
From: Sydney
Status: offline
Jason,
how did you go with the Autodiscover problem ?
I've been struggling with this error since I deploy my Exchange Server 2007 and I've come accross to several sites for the resolution and workaround but it doesn't seems to be helpful anyway :-|, here's the list of the workaround for this Issue of Autodiscover.
I have a hosted Exchange environment so my setup may be slightly different than most users. I got this working by using scenario 4 (Single certificate with Redirect) detailed in this article:
Basically, I have a certificate for my domain as secure.mydomain.com installed on my CAS and the A record pointing to one particular static IP. I then setup another virtual website on the same CAS and had that website listen externally on a second static IP with the host header of autodiscover.mydomain.com and the appropriate external A record. The article talks about how to do IIS redirection, which should be followed very closely. I created an "AutoDiscover" folder in that second website and created a blank text file called AutoDiscover.xml. I then used IIS redirection to point to the correct URL under secure.mydomain.com (https://secure.mydomain.com/autodiscover/autodiscover.xml). I then have my hosted Exchange customers add a CNAME in their own domain to point autodiscover.customerdomain.com to autodiscover.mydomain.com. In other words, when Outlook tries to go to http://autodiscover.customerdomain.com/autodiscover/autodiscover.xml it gets a 302 HTTP redirect from the secondary IIS virtual website I setup to https://secure.mydomain.com/autodiscover/autodiscover.xml.
The article mentioned above talks about this in more detail. Feel free to reply with questions or comments.