For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Simon_Blakely's avatar
Oct 27, 2014

OneConnect and Exchange iApp

What are the consequences of disabling OneConnect on an Exchange iApp?

 

The client is having an issue and the resolution is to disable OneConnect. However, they have an Exchange iApp, so I'd like to know what the consequences are for their Exchange deployment.

 

Thanks

 

3 Replies

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Hi, can you tell us which version of the Exchange iApp and Exchange Server you are using? What's the specific issue?

     

    OneConnect offers performance improvements and is important to the proper functioning of per-request load balancing and persistence.

     

    thanks

     

  • The iApp is 2012_06_08 and it looks like Exchange 2010 at the backend.

     

    The specific issue is nothing directly to do with the Exchange iApp, but requires disabling OneConnect across all virtuals as a workaround.

     

    The question is whether removing OneConnect from the iApp will still allow the iApp to function correctly - it may be the performance penalty will be too great, but I'd like some idea of whether it is even an option.

     

    Thanks

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    First, that's a really old version of the iApp. The latest version is f5.microsoft_exchange_2010_2013_cas.v1.4.0 and is available on downloads.f5.com and I recommend using it because there have been dozens of bug fixes and new features since then.

     

    The iApp should still function correctly. I don't think that Exchange is going to re-use a TCP connection between services.

     

    Here's more info on OneConnect: https://support.f5.com/kb/en-us/solutions/public/7000/200/sol7208.html