ActiveSync for Exchange 2013 ( LTM V12)

Hi Panda 01, mixing versions of BIG-IP in an HA pair can cause unexpected results. I recommend either upgrading both boxes together, or creating new partitions on both that you can upgrade. If it fails after you've upgraded the new partitions on both boxes, you can reboot to your 11.5 partitions.

Here's some guidance on upgrading HA pairs: https://support.f5.com/kb/en-us/solutions/public/11000/300/sol11318.html

(That's for v10, the v11 link is broken).

I don't believe that this is the issue because I broke the trust between the devices and now each one of them is a standalone one, and ofcourse I forced the new version now offline till I figure out how to fix the activesynic for the emails. After when I make sure all application will run smoothly on the new version, I will upgrade the 2nd device and join the trust between them again.

Thanks for your reply

Is every other service working on the 12.0 box, just not ActiveSync? I assume that the ActiveSync pool is marked up by its monitor, correct?

Have you run the MS connectivity analyzer against 12.0?

Hey Guys, I would like to update you that the issue was fixed, so in case anyone face the same issue here's what actually happened.

The health monitor of the ActiveSync pool was down because there is a bug in the new version of F5 (V12.0). This bug affects monitors with usernames by adding an extra backslash.

Hi, We have template 1.5.1 and still having the same bug (with 12.0) Is there a fix for this issue?? Thanks