Forum Discussion
jdewing
Cirrus
CirrusRPC Client Access
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.
22 Replies
jdewingCool.. I have 2 CAS, 2 HT, 4 Mailbox servers. One other things, do you know how to clear the cache on F5?
Ken_107043Nimbostratus
I know very little about the F5...just the basics from trying to get it to work with Exchange, it might be something that is done through SSL/Telnet console though. Are you talking the DNS cache?- jdewingI figured it out.. you connect to F5 device via ssh and run “wa_clear_cache”.
By using the http profile that you created from the deployment guide, it using cache. So when I tried to do some testing with owa for different profile setting, it vary (sometime it work or not). It possible has to do with the cache. From now on, I will clear out the cache for any testing.
Good luck with your project.. Please do let me know what you do to make it work.
Thanks again. 
kfriend_50715I just changed three servers from basic authentication to forms authentication so the OWA page appears and now 1/3 is hanging when I get into OWA. Haven't figured it out yet, but it is an issue. Strange because if I go directly to the server (server1.mydomain.com) in lieu of the external URL for owa which is the LTM (owa.mydomain.com) it works fine, just when going through the LTM I get a hang, can't access email, can't logout or do anything. I'll keep you posted. Still working on getting exchange web services online, the OAB, ECP and dealing with a certificate error I'm getting for outlookanywhere. =/ =/- kfriend_50715JDEWING-
On Friday I tested OWA.
I went to cas1, cas2 and cas3 and all worked fine. I went into the LTM and disabled pool members cas2 and cas3 for the OWA POOL. tested owa.mydomain.com and I received javascript errors hitting cas1 through the LTM. I repeated the process, disabling cas1 and cas3 in the LTM and went to owa.mydomain.com and it worked fine hitting cas 2 through LTM...again, cas3 through LTM was fine...I figured the problem was specific to cas1 and decided to leave it disabled until I could look at it this morning (I have a bunch of other issues I need to work through so it wasn't high priority).
This morning my colleague in Wisconsin tested hitting either CAS2 or CAS3 through the LTM (not sure which because both were enabled) and he received JS errors. I tested and I did NOT receive JS errors. I gave him my test account credentials to ensure it wasn't an issue specific to an account and he still received JS errors. Whatever the issue is, it seems to be specific to the LTM and it's VERY sporadic.
I remember encountering this problem when we were deploying the LTM to begin with. I would report to my colleague that OWA was hanging and he would test it and it would be fine...I would go back in and it was no longer hanging.
I have some other issues to work through first but if I cannot find a quick answer for this I will put in a ticket with F5 and report back to you.
respectfully,
Ken - jdewingYeah, I had exactly the similar issue with the JS errors. I believe it have to do with a setting on HTTP profile.
- kfriend_50715yes, I went back to the default (parent) profile and it seems to be better...haven't tested much but I believe all services are now online and configured correctly...what a pain...nightmare.
Did you narrow down what the setting was that was causing OWA to hang for you? - jdewingIt could be the cache setting that was inheritance from the Parent Profile "http-wan-optimized-compression-caching" or setting “keep accept Encoding”.
As right now, I couldn’t duplicate the issue with the JS errors. I changed the setting back to where it was causing the issue before, but still can’t duplicate the issue. I just don’t get it. It seemed to be working now, but I have no confidence yet.
FYI.. There is an Eseminar “Ensuring High Availability for Client Access to Microsoft Exchange Server 2010” on March 17. It sponsored by F5 and Microsoft. Here some info. http://event.on24.com/eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=287198&sessionid=1&key=587891281B945A04CF88FDBADE8DA2E4&sourcepage=register&partnerref=list2 
Matt_9908I've seen the issues with OWA as mentioned with this thread. I updated the HTTP profile to disable the "keep accept Encoding". This made owa much better, but broke web services connections. My Mac-Office 2011 clients couldn't connect through the URL https://2010_VIP.domain.com/ews/exchange.asmx and availabilty/free busy broke between my 2007 and 2010 systems.
We enabled the keep accept encoding back on to fix web services. I'll be trying a different HTTP profile to see the effects.- jdewingKfriend, How your project going?
