AltostratusWe 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?
AltostratusWe haven't gotten that far yet to look for successful authentications in APM when forwarded to the iApp VS.
Everything is using a wildcard certificate, except that the old VS is using 'Performance (Layer 4)' for the type, so no certificate is used. That's why I was wondering about changing the combined_https VS to 'Performance (Layer 4)' instead of 'Standard'. That was the one thing the stood out as a difference between the old VS and the iApp VS. That being said, the wildcard cert on the Sentry, F5 and Exchange all have different thumbprints, but are all issued from the same primary wildcard certificate from Digicert.
