Forum Discussion
NimbostratusAny reason not to set up Exchange 2013 with the iApp?
I'm going to be running active/active with Exchange 2013 the first system to be put behind my LTM. Is there any reason AGAINST using the iApp template to configure the LTM for Exchange? It's been recommended to me from others, and I see the benefit as someone just learning the BIG-IP platform, but what are the drawbacks, if any?
3 Replies
Cody_GreenEmployee
I always recommend using the latest version of the iApp. Even if you need to make a few modifications after the iApp is deployed it will build a baseline for you and significantly reduce your deployment times.
I have not run across any reasons with my customers on why the Exchange 2013 iApp would be an issue. The iApp itself offers several deployment models to fit your particular deployment.
Note, if you're going to use MAPI over HTTP there are a few configurations you'll have to build by hand but those are documented in the deployment guide.
Cody
Olusola_Ayoade_Hi Cody Green, please help out, i have used OS version 11.6.0 and v1.4 cas iapp Template for loadbalancing exchange 2013, however only outlook anywhere pool is active AD, OWA, AND AS pools are down, my combinned https virtual server is up but the combined http vs shows an unknown status. i can see my virtual server statistics and i can tell that traffic hits the vs but it doesnt get routed to the cas server.
Also my pools are down.
Is it possible to use iapp template and OS Version for exchange 2013 loadbalancing without additional irule.
Kindly assist
- Cody_Green
I would recommend using the latest version of the iApp as outlined in the deployment guide: https://f5.com/solutions/deployment-guides/microsoft-exchange-server-2010-and-2013-release-candidate-big-ip-v11-ltm-apm-afm
Also, make sure you have DNS configured since the Exchange monitors are based on the FQDN of the published Exchange service.
If all else fails switch to TCP or ICMP monitors so you can verify that Exchange is operating successfully.
