Forum Discussion
Exchange 2013 iApp Confguration for MobileIron
- Nov 03, 2016
We resolved this. We had the ActiveSync virtual directory in IIS locked down to the MobileIron servers, but needed to add the self-ip's of the F5 devices as well.
Hi RainHail, You can't change the iApp virtual server type to Performance L4 because that VS type isn't supported for doing all the things that the iApp deployment needs to do.
I'm unfamiliar with how MobileIron works, so I'm just going to ask some general questions.
Is MobileIron sitting between mobile clients and your Exchange server? Was the previously configured Performance L4 virtual server the target for traffic sourced from MobileIron, and did it work until you switched it to point at the iApp-created virtual server?
Did you deploy APM or AFM with your Exchange iApp?
It's hard to do much more troubleshooting without knowing exactly where it's breaking. We'd want to verify that the request is getting to the iApp virtual server and if it's making it through to the ActiveSync pool on the back end. You can turn up the APM log level to debug and watch /var/log/apm to verify that you are getting an authenticated session. You should also be able to add an iRule to the iApp VS to log the ActiveSync requests and responses from Exchange.
I recommend opening a case with F5 support on this. If you want, you can send me the case number so I can track it.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com