Forum Discussion

Sundar_Sivasank's avatar
Sundar_Sivasank
Icon for Nimbostratus rankNimbostratus
Apr 09, 2014
Solved

iApp exchange 2013 Login issue

I am using the latest iApp deployment guide for exchange 2013 on LTM v11.5. I see that the iApp doesnt add any persistent profiles for owa. After i just use the iApp to deploy and try to login to my OWA, i am again thrown the same OWA login screen again. This behaviour is without having any persistence. But when i just added a source address persistence to the virtual server, i see that i can successfully login. So my query is the persistence definitely needed for OWA to work? If thats the case why is it that the iApp doesnt include the persistence as part of its template? Also, if the persistence is surely needed, please do let me know the F5 recommended persistence that should be used for different services in exchange 2013. It would be really helpful if someone could help me clarify my query. Thanks in advance.

 

Regards Sundar

 

application delivery
deployment
design
devops
iApps
LTM
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Apr 09, 2014

    I found the info from the last time I encountered this problem. Are you doing SSL bridging? If so, do the certificates on your CAS contain the host name used to access OWA, and do they both match the cert you're using to decrypt on BIG-IP?

     

9 Replies

Sort By
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Apr 09, 2014

    Hi Sundar, persistence is not required for OWA 2013.

     

    I ran into this issue before, and IIRC it's a configuration on the Client Access Server. I can't remember off the top of my head what the setting was. Are you able to post the output of the Powershell command "Get-OWAVirtualDirectory"?

     

    thanks

     

    Mike

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Apr 09, 2014

    I found the info from the last time I encountered this problem. Are you doing SSL bridging? If so, do the certificates on your CAS contain the host name used to access OWA, and do they both match the cert you're using to decrypt on BIG-IP?

     

    • Sundar_Sivasank's avatar
      Sundar_Sivasank
      Icon for Nimbostratus rankNimbostratus
      Apr 10, 2014
      Hi Mike, First of all thanks for your response. Yes we are doing SSL Bridging. Currently, all the certs we are using are self signed certs and as mentioned by you the certificates arent the same. So to confirm, i need to have the same certificate/private key as the OWA server on my Big IP for decrypting? Is my understanding correct?
    • mikeshimkus_111's avatar
      mikeshimkus_111
      Historic F5 Account
      Apr 10, 2014
      That's correct. You can use a self-signed cert, but you need to copy it to and import it on all your CAS, as well as the BIG-IP.
    • Sundar_Sivasank's avatar
      Sundar_Sivasank
      Icon for Nimbostratus rankNimbostratus
      Apr 10, 2014
      Thanks Mike. Just another clarification, can i know why exactly there is no need for persistence in Exchange 2013? Is it because of the exchange 2013 behaviour? Also how does the certificate really impact the persistence? Thanks Sundar
  • Olusola_Ayoade_'s avatar
    Olusola_Ayoade_
    Icon for Nimbostratus rankNimbostratus
    Mar 05, 2015

    Hi Mikeshimkus,

     

    Please assist have an issue on site OWA on exchange 2013 is been load balanced effectively but outlook has ssl certificate errors and its not connecting , please assist i need to know why owa is effectively load balanced but Outlook cant connect.

     

    Regards