F5 RPC Client Access, Autodiscover design
Hi
New to working with F5 and I am just after some clarification on our setup, LTM and APM are the same device. This was done by an external consultant.
We are looking at using the device for OWA, Activesync, Outlook RPC Client Access (MAPI), Autodiscover.
What we have had setup is
1 iapp application service using BIG-IP virtual server 10.100.100.231 With OWA, Outlook Anywhere, ActiveSync set to YES Autodiscover, RPC Client Access (MAPI), POP3, IMAP4 set to NO And referring to CAS 10.100.100.55 (this is OWA server)
3 Virtual Servers using 10.100.100.231 – Exchange 2010 using the application above 10.100.100.232 – Exchange Autodiscover –using Pool (using Pool 10.100.100.53, 10.100.100.54) they are our CAS / HT 10.100.100.232 – Exchange Internal RPC Client Access –using Pool (using Pool 10.100.100.53, 10.100.100.54) they are our CAS / HT
My query - what I am unsure about is why the Virtual Servers are on different IP unless I need to setup another iapp for Autodiscover/ RPC Client Access. OWA works fine through F5
Also for exchange my understanding to get RPC and Autodiscover is I need to configure a few steps, can someone confirm these. 1.Configure Client Access Array 2.Configure Static RPC Ports on an Exchange 2010 Client Access Servers 3.Enable SSL Offloading on the Client Access Servers.
4.Update A and SRV records to point to either 10.100.100.231 or .232
Thanks in advance