Moved Exchange 2010 from Cisco ACS to F5 LTM

We have an other installation 11.3 using the rc1 iapp and I can see that the uglobal.js have been exclude.

 

Should I try this also?

Jan, the uglobal.js caching exclusion only applies to OWA traffic.

 

 

The only things being cached when using the fat Outlook client are the Offline Address Book .lzw files. There shouldn't be any impact on accessing a shared mailbox.

 

 

Also, the iRule addresses any instances where OneConnect needs to be disabled. Can you post the contents of your exchange2010_combined_persist_irule7 here?

 

 

I will give it a test today and see if I can reproduce the problem.

 

thanks

 

Mike

I was not able to reproduce this; I can access shared mailboxes via both MAPI and Outlook Anywhere clients and they update without issue.

 

 

I did find a Technet post about a similar problem: http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/b2edd2f5-15c6-405a-b2fd-c365d4fa7e6f/

 

 

Do you have your account set to download shared folders in cached mode?

 

Mike

The shared mailbox is in cached mode.

 

 

Here is the exchange2010_combined_persist_irule7

 

Jan

 

 

iRule to select pool and persistence method when all HTTP-based services are

 

accessed through the same virtual server. This iRule uses an HTTP header

 

inserted by a BIG-IP Edge Gateway for persistence (if that header is present)

 

Otherwise it will set persistence according to traditional methods.

 

when HTTP_REQUEST {

 

switch -glob -- [string tolower [HTTP::path]] {

 

"/microsoft-server-activesync" {

 

Direct all ActiveSync clients to a common pool; use Auth

 

header value if it exists (Basic auth only, which is the

 

default); otherwise we fall back to client IP

 

if { [HTTP::header exists "APM_session"] } {

 

persist uie [HTTP::header "APM_session"] 7200

 

} elseif { [HTTP::header exists "Authorization"] } {

 

persist uie [HTTP::header "Authorization"] 7200

 

} else {

 

persist source_addr

 

}

 

pool ad_global_exchange2010_as_pool7

 

COMPRESS::disable

 

CACHE::disable

 

return

 

}

 

"/owa*" {

 

Outlook Web Access

 

if { [HTTP::header exists "APM_session"] } {

 

persist uie [HTTP::header "APM_session"] 7200

 

} else {

 

persist cookie insert 0

 

}

 

pool ad_global_exchange2010_owa_pool7

 

return

 

}

 

"/ecp*" {

 

Exchange Control Panel.

 

if { [HTTP::header exists "APM_session"] } {

 

persist uie [HTTP::header "APM_session"] 7200

 

} else {

 

persist cookie insert 0

 

}

 

pool ad_global_exchange2010_owa_pool7

 

return

 

}

 

"/ews*" {

 

Exchange Web Services.

 

if { [HTTP::header exists "APM_session"] } {

 

persist uie [HTTP::header "APM_session"] 7200

 

} else {

 

persist source_addr

 

}

 

pool ad_global_exchange2010_oa_pool7

 

COMPRESS::disable

 

CACHE::disable

 

return

 

}

 

"/oab*" {

 

Offline Address Book. Persistence is not required for OAB

 

pool ad_global_exchange2010_oa_pool7

 

return

 

}

 

"/rpc/rpcproxy.dll" {

 

if { [HTTP::header exists "APM_session"] } {

 

persist uie [HTTP::header "APM_session"] 7200

 

} elseif { [string tolower [HTTP::header "Authorization"]] starts_with "basic" } {

 

persist uie [HTTP::header "Authorization"] 7200

 

} else {

 

persist source_addr

 

}

 

Outlook Anywhere.

 

pool ad_global_exchange2010_oa_pool7

 

COMPRESS::disable

 

CACHE::disable

 

return

 

}

 

"/autodiscover*" {

 

Autodiscovery. No Persistence.

 

pool ad_global_exchange2010_ad_pool7

 

return

 

}

 

default {

 

This final section takes all traffic that has not otherwise

 

been accounted for and sends it to the pool for Outlook Web App

 

if { [HTTP::header exists "APM_session"] } {

 

persist uie [HTTP::header "APM_session"] 7200

 

} else {

 

persist source_addr

 

}

 

pool ad_global_exchange2010_owa_pool7

 

}}

 

}

 

when HTTP_RESPONSE {

 

if { [string tolower [HTTP::header values "WWW-Authenticate"]] contains "negotiate"} {

 

ONECONNECT::reuse disable

 

ONECONNECT::detach disable

 

NTLM::disable

 

}

 

if {[HTTP::header exists "Transfer-Encoding"]} {

 

HTTP::payload rechunk

 

}

 

}

 

Yes, I realized that you meant Outlook cached mode once I started testing. The iRule looks fine, and I wasn't able to reproduce the problem. I recommend that you open a case with F5 support on this, and send me the case number in a private message so I can follow it.

Thank you Mike,

 

After reboot of all of the servers it working better now.

 

Let me and some other users do some more test before we open a case with F5.

 

 

Jan

Hi,

 

I have setup a new VIP with the new iapp rc3 and everything works great now.

 

Jan

Hi all,

 

 

I'm having problems with Macintosh EWS Mail clients using the 06_08 Exchange iApp with Big-IP 11.2.1 HF6. I've got a support call open with F5, and I've been advised to disable the Exchange analytics profile, which oddly enough fixed my issue with Apple Mail, but not with Entourage.

 

 

This iApp seems useless, it needs to work with all supported Exchange 2010 clients, not just the basics of OWA, Active Sync and MAPI. All EWS clients need to work, otherwise we can't use the product.

 

 

I've seen a number of times in forums F5 engineers suggesting that customers use the yet to be finalised and still formally unsupported RC3-4 for Exchange 2010 and 2013. How on earth are you guys recommending that we use your beta software for our production services?! F5 hardware and licences cost a premium and we can't be expected to tiral out your software for you in the field.

 

 

Please can someone get back to me as soon as possible with some answers. I need to know which version of your iApp is supporting for Exchange 2010, using a mixture of mail clients including Mac OSX, and running on Big-IP 11.2.1 HF6. Please don't tell me that I need to upgrade Big-IP to get a later iApp, we've only just upgraded to this code level, and there are no functional issues with it for us, apart from the Exchange iApp.

 

 

Please F5, how about some straight answers here?

 

 

Gavin Connell-Otten

 

Victoria University Wellington

Hi all,

 

 

I'm having problems with Macintosh EWS Mail clients using the 06_08 Exchange iApp with Big-IP 11.2.1 HF6. I've got a support call open with F5, and I've been advised to disable the Exchange analytics profile, which oddly enough fixed my issue with Apple Mail, but not with Entourage.

 

 

This iApp seems useless, it needs to work with all supported Exchange 2010 clients, not just the basics of OWA, Active Sync and MAPI. All EWS clients need to work, otherwise we can't use the product.

 

 

I've seen a number of times in forums F5 engineers suggesting that customers use the yet to be finalised and still formally unsupported RC3-4 for Exchange 2010 and 2013. How on earth are you guys recommending that we use your beta software for our production services?! F5 hardware and licences cost a premium and we can't be expected to tiral out your software for you in the field.

 

 

Please can someone get back to me as soon as possible with some answers. I need to know which version of your iApp is supporting for Exchange 2010, using a mixture of mail clients including Mac OSX, and running on Big-IP 11.2.1 HF6. Please don't tell me that I need to upgrade Big-IP to get a later iApp, we've only just upgraded to this code level, and there are no functional issues with it for us, apart from the Exchange iApp.

 

 

Please F5, how about some straight answers here?

 

 

Gavin Connell-Otten

 

Victoria University Wellington

Hi all,

 

 

I'm having problems with Macintosh EWS Mail clients using the 06_08 Exchange iApp with Big-IP 11.2.1 HF6. I've got a support call open with F5, and I've been advised to disable the Exchange analytics profile, which oddly enough fixed my issue with Apple Mail, but not with Entourage.

 

 

This iApp seems useless, it needs to work with all supported Exchange 2010 clients, not just the basics of OWA, Active Sync and MAPI. All EWS clients need to work, otherwise we can't use the product.

 

 

I've seen a number of times in forums F5 engineers suggesting that customers use the yet to be finalised and still formally unsupported RC3-4 for Exchange 2010 and 2013. How on earth are you guys recommending that we use your beta software for our production services?! F5 hardware and licences cost a premium and we can't be expected to tiral out your software for you in the field.

 

 

Please can someone get back to me as soon as possible with some answers. I need to know which version of your iApp is supporting for Exchange 2010, using a mixture of mail clients including Mac OSX, and running on Big-IP 11.2.1 HF6. Please don't tell me that I need to upgrade Big-IP to get a later iApp, we've only just upgraded to this code level, and there are no functional issues with it for us, apart from the Exchange iApp.

 

 

Please F5, how about some straight answers here?

 

 

Gavin Connell-Otten

 

Victoria University Wellington