Moved Exchange 2010 from Cisco ACS to F5 LTM

Hi Jan,

 

First question, are you using the latest version of the Exchange iApp available here: https://devcentral.f5.com/wiki/iApp.Microsoft-Exchange-2010-and-2013-iApp-Template.ashx

 

?

 

 

To address each of your questions:

 

1. This will be addressed in the next release of the iApp template. We recommend going to the properties page of the web acceleration profile, typing oab.xml into the URI box (URI caching should be enabled) and then clicking the Exclude button. This will cause oab.xml to be excluded, but not the address book files themselves. We still want to cache those files, since they can be quite large.

 

2. What changes were made last Wednesday? I assume you are using POP or IMAP and that the pools for those services are up? What errors do clients get?

 

3. Not sure about this, do you know what changed a few weeks ago? Does the intended recipient address still exist?

 

4. Free/busy uses EWS, so the status of Autodiscover isn't necessarily related. I like to use the EWS Editor to test EWS and Autodiscover: http://ewseditor.codeplex.com/. Knowing the version of the iApp template you are using will help with this as well, since there have been changes from earlier versions that have affected EWS.

 

 

thanks

 

Mike

Hi Mike,

 

We have 11.2.1 with sp5 installaed and I have used the iapp f5.microsoft_exchange_2010_cas.2012_06_08

 

Should I use RC or not for the iapp?

 

 

Let me test the other sugestion tomrrow.

 

 

Jan

Yes, I recommend using the RC2 version.

I used the iapp RC2 and created the all from the beggning, with new ip numbers and the download of the of the GAL who was one of the problem, is gone now. :-)

New problem wit RC2, any known issue?

 

 

OAB was solved, but we encountered another issue that “shared mailboxes” were not updated properly.

 

After going back to the ACE, it started to work immediately.

Can you give more detail? Are you trying to view free/busy data, or...?

The settings in LTM seems to be right, but we have nevertheless the problem that “linked/additional” mailboxes are not working properly.

 

They can be accessed, but are not being updated with new incoming mail over the F5.

 

All secondary mailboxes attached to your outlook profile are not being updated (no new mails coming in)When manually updating the folder by “Update Folder” does not work either – we know there is new mail as we can see in the webmail, but they are not being shown in the outlook profiles.

 

 

After changing back to the Cisco ACE load balancer it all works again.

 

 

Mike,

 

 

Could this be a cache problem with shared mailbox?

 

Found this old forum https://devcentral.f5.com/community/group/aft/2163427/asg/62

 

 

Jan

The problem mentioned in that thread actually has to do with OWA, not Outlook, and it's one specific Javascript file that needs to excluded from the cache. Your issue is with shared mailboxes accessed by the regular Outlook client, correct? Is that Outlook Anywhere or MAPI?

The issue is with regular outlook and shared mailboxes.

 

 

We believed that the issue with the shared mailboxes is on MAPI access if the shared mail box is cached.

 

But yesterday we got the same symptoms with both outlook anywhere and RPC over the F5.

 

I also think that the problem above with MAC is oneconnect or cache issue.

 

I found some old problem on the forum that disable oneconnect solve the problem.

 

If I should try to disable the cache and oneconnect I need fix the irule exchange2010_combined_persist_irule7 that was created with the iapp.

 

Or mabye I can remove the irule and then disable the cache and the oneconnect, to see if thie fix our issues.

 

But again it should be nice to use oneconnect and the cache on.

 

Jan