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

alphonse's avatar
alphonse
Icon for Nimbostratus rankNimbostratus
Apr 24, 2014

Does F5 support Exchange 2010 SP3 ?

Hi , I am running 11.4.0 - Hotfix HF3 with exchange 2010 SP2, all going well. but After upgrading the exchange from 2010sp2 to 2010 sp3 rollup 5. I got error code 403 when connecting to outlook.

 

I'm looking for this sol http://support.f5.com/kb/en-us/solutions/public/13000/400/sol13497.html, but I don't see that 2010sp3 is listed. Please do you know if 2010sp3 is supported when running 11.4.0HF3 ?

 

In advance thank you.

 

9 Replies

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Hi alphonse, we do currently support 2010 SP3, per the deployment guide:

     

    https://www.f5.com/pdf/deployment-guides/microsoft-exchange-iapp-v1_3-dg.pdf

     

    Have you bypassed the BIG-IP to see if you still get the 403 error when connecting directly to the CAS?

     

    thanks

     

    Mike

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    This is Outlook Anywhere, correct? Are you using the v1.3 Exchange iApp template to deploy? Are you deploying an Analytics profile on your virtual server? If so, remove it.

     

  • it's correct for Outlook Anywhere. we use Exchange iApp v1.3 and Analytics profile is not on.

     

    thk

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Is it possible to get a capture of the HTTP request sent from the BIG-IP to the CAS that is producing the 403 error?

     

  • Mike, I have checked again the iapp version is v1.3 , I will upgrade to v1.3. Come back soon thk

     

  • Sorry

     

    Mike, I have checked again the iapp version is v1.2 , I will upgrade to v1.3. Come back soon thk

     

  • Hi Mike, I have a good new, from the tcpdump I see that the server send 403 error code to the client. this is the SSL offloading issue.

     

    http://social.technet.microsoft.com/wiki/contents/articles/1267.how-to-configure-ssl-offloading-in-exchange-2010.aspx?wa=wsignin1.0Configuring_SSL_Offloading_for_Autodiscover_Service_AS