I am trying to load balance our Exchange 2013 CU7 environment with Citrix Netscaler. I am trying to start the process to migrate our users from 2010 SP3 to 2013 CU7. Every once in a while I experience a looped login when trying to login to OWA. You enter your username and password and it loops right back to the login page... stopping you from ever logging in.

This made me think it was something with session affinity on the load balancer... however I thought they didn't need that anymore. So I'm wondering if since i'm in coexistence with 2010 it still is required.

I have no users on 2013 yet so all my test accounts are on 2010.

My environment:

• 3x Exchange 2013 CU7 CAS/MBX combined
• 3x Exchange 2010 CAS
• 3x Exchange 2010 MBX
• 2x Citrix Netscaler 10.5 VPX

Does anyone know the proper way to configure this? Information on Netscaler for this would be great but it doesn't have to be related to Netscaler. I'm just looking for the proper session affinity values for Exchange 2013 with 2010 coexistence.

Hi quadrantids,

Thank you for your question.

Whats URL when you login OWA?

Did you try to login OWA by the following URL: https:// FQDN of Exchange/owa  

Could you tell me more details which is about load balance configuration on Exchange 2013?

If we could access OWA by https:// FQDN of Exchange/owa, we could check the configuration of load balance.

If we could not access OWA by https:// FQDN of Exchange/owa on the specific Exchange CAS server, we could reset IIS on Exchange CAS server.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Also, which guide/article you are following to accomplish your task ?

Please take a look on Exchange server deployment assistant that available from Microsoft team and provides step-wise instructions to manage this job in more easier way : https://technet.microsoft.com/en-us/office/dn756393.aspx

If the still unable to configure the setting and achieve this goal, I would suggest you to have a look on this automated solution (http://www.exchangemailboxmigration.com/) that could be a good alternative solution for you.