Updated 2/24/2011 • Originally posted on 24-Feb-2011 by
I'm having an issue getting outlook client to work with RPC Client Access. I follow the steps from the F5 Deployment Guide "Microsoft Exchange 2010". Everything is working with OWA and Hub Transport, but just not with RPC Client Access. I tried so many different settings for VIP, no luck. 1. Created a DNS “A” record for outlook.xxxx.local 2. Created a Client Access Array and associate it with outlook.xxxx.local 3. Follow steps from the Deployment Guide to create health monitor, pool, profile and VIP 4. Created a new Outlook Profile and pointed to outlook.xxxx.local. This is where I’m stuck.. I can’t get the outlook client to communicate with the CAS. When I created outlook profile, I enter outlook.xxxx.local for Microsoft Exchange Server, I get error “The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action” However I could enter the CAS Server name “CAS01.xxxx.local” for Microsoft Exchange Server with no issue, but the correct way is to use the RPC Client Access name for load balancer. Did anyone had a similar issue and able to get it resolve??? Thanks in the advance.