LTM Error When Users Disconnect from Exchange

Hi Jared-

 

 

I haven't looked up your case yet but will do so shortly.

 

 

However, yes, you'll definitely want to use f5.microsoft_exchange_2010_cas.2012_06_08. There are a large number of fixes -- pretty much all of the items that previously had to be done with strict updates off -- thatt address client connectivity and authentication issues. (Most were caused by interactions between F5's OneConnect feature and NTLM authentication, but there were other subtle issues as well). The new version now also allows you to select custom iRules to attach to virtual servers without disabling struct updates, so you can modify or create custom behavior without leaving the iApp.

 

 

An upgrade will wipe out any changes you made with strict updates disabled, so what I'd actually suggest is this:

 

 

1) Install the newer iApp template. (This is a safe operation and won't touch anything with your current configuration.)

 

 

2) Obtain 2 additional IP addresses.

 

a. IP1 is the address you're currently using on your virtual server.

 

b. IP2 is a new address for a new virtual server.

 

c. IP3 is used temporarily and doesn't even have to be something that is real/accessible.

 

 

3) Deploy a new configuration using the 2012_06_08 version of the iApp and assign IP2 to that virtual. The iApp template will prompt you for all the settings it needs and will allow you, for instance, to combine services such as OWA, Outlook Anywhere, Autodiscover and ActiveSync on the same virtual server.

 

 

4) Test some clients using that virtual server, perhaps using a local 'hosts' file to force them to connect there rather than the original one.

 

 

5) If you're satisfied with results, but want to keep the original config just to be safe or for future reference, wait for a service window and then do this:

 

a) assign IP3 to the original config.

 

b) switch the new config to use IP1

 

 

Of course, you can use a different order of the above to just switch the new config to be the primary right away and test that way (instead of using host files), if your policies, service window and users' tolerance permit ;)

 

 

-Dayne