Forum Discussion
john_doe_103663
Nimbostratus
Nimbostratusexchange 2007 autodiscover
I have exchange 2007 cas servers behind my f5 ltm v9x I can get webmail and outlookanywhere working, but my problem is with the autodiscover service. Since my https is being terminated on the bigip which has a san ucc certificate and talkes with my exchange cas through http. I know the autodiscover service uses 443 and download a xml file from the cas.
but my client on the internal lan can get the autodiscover service but thats propably going through a scp in active directory.
does anybody ever successfully configed autodiscover to work with f5
hoolioCirrostratus
Are there references to http:// URIs in the xml file or the servers respond headers and/or other data? If so, there might be a configuration option or HTTP header you can set to instruct the server to use HTTPS references even though it's communicating via HTTP. There is an option for OWA like this (setting 'Front-End-Https: On' header and value in requests). Or you could potentially rewrite the http:// references to http:// using a stream profile and STREAM::expression iRule (Click here).
Aaron
john_doe_103663no its all https:// in the uri
gfv9098_32461Hello,
Did you ever get this working? We seem to be having a similar problem.
Thanks,
Peter_ReillyThere may well be better ways to accomplish autodiscover support, but we added a vip for autodiscover.our_domain_name for https, pointing it to the same pool, with an irule redirecting blank uri's to the owa server.
when HTTP_REQUEST {
if { [HTTP::uri] equals "/" } {
redirect to "https://my_owa_server/exchange"
}
}
Luca_55898Anyone know if this ever got resolved?- Luca, Check out page 14 of the Exchange 2010 deployment guide: http://www.f5.com/pdf/deployment-guides/f5-exchange-2010-dg.pdf
There's also an iRule in the guide for disabling oneconnect for autodiscover.
I haven't tried this config with Exchange 2007 but it may help you.