iRule to Redirect autodiscover traffic
Dear all, the SSL certificate in my current virtual server points to autodiscover.abc.com and not autodiscover.abccommodities.com I would like F5 to redirect from autodiscover.abccommodities.com to autodiscover.abc.com in hopes to eliminating the SSL security warning popup from Outlook clients as seen below. Is that possible? I tried this iRule but it wasn't working, still prompts warning. I believe Outlook client is using HTTPS traffic to contact the mail server? when HTTP_REQUEST { if { [string tolower [HTTP::host]] ends_with ".abccommodities.com" } { HTTP::redirect "https://autodiscover.abc.com" } }
AutoDiscover Issue with Exchange 2016 iApp
Hello together, got one big problem: I have deployed successfully the iApp template of Exchange 2016 and the customer wants to use OWA and AutoDiscover Service. The AutoDiscover Service is not working as expected.. so the user cannot authenticate with e-mail or domain\username. My Access Policy: Logon Page (Split Domain from full Username YES) -> AD Query (Cross Domain Support DISABLED) -> AD Auth (Cross Domain Support ENABLED) -> SSO Credential Mapping (default). I used the right Domains and Access Profiles. OWA is a logon possible with E-Mail, User and domain\User. But AutoDiscover is just User and domain\User. E-Mail is NOT working. Does anyone know, how the users could finally authenticate via E-Mail? They're claiming that they're not able to use AutoDiscover Thanks in Advance! HankCan LTM help to save on SSL certificates on different common names?
Dear all, F5 had recently replaced Brocade and Microsoft Forefront Threat Management Gateway (Forefront TMG). Customer has many subsidiary companies and has its own domain names. They all point to a public IP and in term being NAT-ed to F5's VIP. There was an SSL cert in this virtual server and is currently presenting mail.abc.com. That is why no security warning when user browses to mail.abc.com/owa on a browser. Customer was unable to tell me what TMG is doing for their environment and he wanted F5 to help with the below issue The issues lies with Outlook Clients connected to external networks, for example employee works from home and is away from their internal network. There is a security warning prompt on Outlook which looks like: Customer told me there wasn't any issue before F5 came into the picture. I nearly wanted to tell him he should buy additional SSL certs but realized he has too many subsidiaries in his environment, connected to his exchange server farm. This issue occurs whenever user setup email client via autodiscover and it pops up occasionally after the email has been setup. User just needs to click YES to acknowledge the warning and they are good to go. But it keeps popping up now and then.OWA iApp Exchange 2016 - AutoDiscover not working
Hey since I deployed OWA iApp via F5 for a customer they claim that AutoDiscover is not working anymore. How can that be? OWA was running before on a TMG and now on F5. Since the change of IP/DNS to make it productive, the customers claiming that AutoDiscover is not working. My Access Policiy is like this: Start --> Logon Page --> AD Auth --> SSO Credential Mapping The single configuration parameters are kept basic (like template). Maybe it has something to do with "Cross-Domain Support"? or "Split Username from domain"? Thanks! Would be nice of somebody could help me, this case is pretty urgent..
