The new, fully supported iApp template for Exchange 2016 has been released to downloads.f5.com in the root directory. Use the deployment guide or the AskF5 solution for instructions on downloading the iApp template. An updated deployment guide is now available at
Microsoft Exchange 2016 rc1
Use this F5 contributed, release candidate iApp template for Microsoft Exchange Server 2016 deployments. Until the accompanying deployment guide for 2016 is released, use the inline help for assistance in configuring the iApp for Exchange 2016.
Exchange 2016 Deployment Guide references an iAPP available in versions 11.4.1 - 12.1. However, it is not present in 11.5.4.
Hello Mike, the iApp is downloadable, and does not ship with the BIG-IP by default (if fact, you should only be using downloadable iApps for Exchange of any version, and not the Exchange 2010 that ships on the box). The deployment guide and the solution linked above both have instructions on downloading the iApp for Exchange 2016. Note that this template is fully supported by F5 networks support.
I tried to use the iApp at customer site but have trouble with it. We are working with software 11.6.0 and apm/ltm setup.
The exchange mrsproxy test (Powershell Command: Test-MigrationServerAvailability -ExchangeRemoteMove -Autodiscover -EmailAddress ... -Credentials ...) is failing because the application profile for exchange does provide only basic and ntlm www-authentication header, but mrsproxy is expecting a negotiate www-authentication header.
If I disable the application profile mrsproxy is working (header with negotiate now offered to client), but in turn autodiscover is not working any more.
Is there anything I missed? I found the extra irule for mapi-over-https wihtin deployment guide and included it. But is there anything other to do?
Lars, did you try the iRule on page 69 of the deployment guide: https://www.f5.com/pdf/deployment-guides/microsoft-exchange-2016-dg.pdf
That should allow the necessary requests for EWS and Autodiscover to pass through APM directly to the server.
Thanks for the answer. I tried something similar - but in a not very sophisticated way. I will try the iRule.
As a feedback: The irule from page 69 seems to do the job so far. We also discovered the exchange powershell testcommand needs a user with administrative rights.