Citrix Netscaler – Loadbalancing Exchange 2016/2019 (Walkthrough Guide)

Reading Time: 11 minutes

If you get the task to load balance Exchange with NetScaler you will find a lot of whitepapers from Citrix with missing information and false configuration recommendations. I was bumping my head against the wall until I got a running configuration with all desired features. Here is the complete walkthrough guide to setup your Exchange environment with a single public ip address. Additional features like AAA, Front End Optimization  and Integrated Caching will depend on your current NetScaler licence.

Change Log

– Emails with attachments never leave Outbox via RPC/MAPI/EAS
Thanks @ Julian Jakob
– Updated expressions for the Authorization Policies (AAA.USER)
– Fixxed missing binding point for Traffic Session Policy “tm_pol_exchange2016_owa_sso” on the AAA vServer. Thanks @ Christian Demmerer
– AAA-default settings changed with Citrix ADC (NetScaler) 13 build 41.20
– Added 401 Based Authentication for MAPI, RPC, OAB, EWS
– Added Group Filtering for OWA, Outlook Anywhere and ActiveSync
– Changed Persistence for the RPC/MAPI LB vServer from RULE to SOURCEIP
– Increased timeout from 240 to 30 minutes (RPC/MAPI)

Feature Matrix


Load Balancing

Content Switching



Front End Optimization

Integrated Caching


















Network Topology



  • One public ip address
  • Two private IP addresses (Content Switch and Load Balancer)
  • Working DNS/NTP on NetScaler
  • Wildcard SSL certificate

Firewall Rules






DNS Server




NTP Server

UDP 123



Domain Controller

TCP 389



Domain Controller

TCP 636



Exchange Server

TCP 25, 465, 587

SMTP Monitor


Exchange Server

TCP 25, 465, 587



Exchange Server

TCP 143, 993



Exchange Server

HTTPS – 443

OWA, AutoDiscover, ActiveSync, MAPI, etc.



TCP 25, 465, 587




TCP 143, 993



Content Switch VIP

HTTP – 80

Web Traffic


Content Switch VIP

HTTPS – 443

Web Traffic

If you dont load balance DNS/LDAPS/NTP the traffic will flow from the NSIP. In my setup the servers are load balanced –> The SNIP is communicating with the backend servers.







Standard Parameter

Send String






“GET /owa/healthcheck.htm”




“GET /Microsoft-Server-ActiveSync/healthcheck.htm”




“GET /rpc/healthcheck.htm”




“GET /ews/healthcheck.htm”




“GET /Autodiscover/healthcheck.htm”




“GET /mapi/healthcheck.htm”




“GET /ecp/healthcheck.htm”

Service Groups











































Load Balancer


IP address





Authentication (AAA)


Least Connection





Least Connection





Least Connection






Least Connection


















Least Connection






Least Connection






Least Connection






Least Connection





Content Switch













































AAA (Enterprise)

If you have an enterprise licence you can let take the authenication on the AAA server and redirect the credentials to OWA. This feature offers improved security integration and n-factor authentication like RADIUS, SAML and certificate authentication is possible. If you enter the mail domain you will be redirected to the AAA login page.


If you want to you use “401 Based Authentication” on the Autodiscover service you need to set the following registry key in the user profile.

Otherwise Outlook 2016 is crashing while setting up the profile (ADAL is enabled by default)
NetScaler is not supporting ADAL at the moment.

Update (2018-05-23): When using NetScaler >= 12.0 there is no need to create the “EnableADAL” key.

Update (2019-10-28): Johannes Norz reached out to me that there is a problem with the authentication when running the Citrix ADC on firmware 13.41.20 and higher. You  will receive the message “Error: Not an privileged user” after the succesfull authentication. Citrix changed the default authorization action to “DENY” which is causing the issue. You can change it back to “ALLOW” or create an authorization policy. For more information check his blog post.

Update (2020-11-02):  Julian Jakob informed me that it can happen that mails with an attachment will never leave the outbox when working in RPC/MAPI/EAS mode. In Outlook you will receive the message “Cannot Procedure”. After disabling AAA for preauthentication everything was working fine. After enabling AAA any mail attachment < 10 KB was sent succesfully. Everything > 10 KB stays in the outbox. After going through the syslog messages he found the following hint “SSO: Special Post request SSO handling initiated for session-id:37295 content-length 980KB”. This brought him to CTX225681 which is saying you should modify the handling of post requests when uploading large files. Execute the following command on the ADC shell to fix the issue:



Authentication Policies

In this setup we  will authenticate with LDAP only. For this we need create two policies.

1.) LDAP with sAMAccountName
2.) LDAP with userPrincipalName

The user can login with “test” or “test@lab.local”.


SSO Traffic Policies

The priorty of the AAA content switch policy must be the one with the lowest priority.

Group Filtering

If you need to restrict the external access to security groups in Active Directory, create the following authorization policies.

Bind the authorization policies to the vServers.

When your user is not in the “External-OWA” group and the authentication against the AAA server was succesfull you will get the following notification:

“Error: Not a privileged User.”

I created a responder html page, to present a more user friendly message. This can’t be done via CLI. Go to AppExpert –> Responder –> HTML Page Imports

2018-05-23 15_02_53-Citrix NetScaler VPX - Configuration

Now you can create the responder policy & action.

Front End Optimization (Enterprise)

I couldnt test this feature too much so I configured like descriped in the Citrix whitepaper. If the optimization action “Moderate” is not suiting your expectations you can try the “Aggresive” mode. You can verify if FOE is working within the GUI. Go to Optimization –> Front End Optimization –> Statics (“stat feo” in CLI)



Integrated Caching (Platinum)

In the Citrix docs its recommended to allocate less than half of the NetScalers memory for integrated caching. Set the parameter “memLimit” fitting to your appliance. I’m using 500MB. You can verify if the cache is working within the GUI. Go to Optimization –> Integrated Caching –> View Cache Objects (“show cache object” in CLI)




I hope this guide helped you to load balance Exchange with Citrix NetScaler.
If you find any misconfigurations or have improvments please contact me.


  1. hi julian, awesome blog thank you for that, and i love to have directly the netscaler commands not the GUI. i did create after 2 days same netscaler config, but for me in all of this guides, it is not normal to make also the loadbalancing steps also for the SMTP and IMAP Traffic? I mean, what is the BestPractice here? Only Loadbalance SMTP Port25 or also Port 587, 143 and so on? Or did that make Exchange 2016 with other Tools? regards frank

  2. hi julian, i have make this, only on the monitors i am not sure, if there is maybe a better monitor as http-evc

    # Create and Bind LB Server for SMTP Traffic / only for SMTP Traffic / when you want / must be configured with Exchange Admin / Relay Rules than on Netscaler
    # Create and Bind LB Server for SMTP Traffic Port 25 and Port 465 and Port 587 and also IMAP Port 143
    add serviceGroup lb_svg_exch2016_smtp TCP
    add lb vserver lb_exch2016_vsrv_smtp TCP 25
    bind lb vserver lb_exch2016_vsrv_smtp lb_svg_exch2016_smtp
    bind serviceGroup lb_svg_exch2016_smtp exchange01.your.domain 25
    bind serviceGroup lb_svg_exch2016_smtp exchange02.your.domain 25
    bind serviceGroup lb_svg_exch2016_smtp -monitorName tcp
    add serviceGroup lb_svg_exch2016_smtp_587 TCP
    add lb vserver lb_exch2016_vsrv_smtp_587 TCP 587
    bind lb vserver lb_exch2016_vsrv_smtp_587 lb_svg_exch2016_smtp_587
    bind serviceGroup lb_svg_exch2016_smtp_587 exchange01.your.domain 587
    bind serviceGroup lb_svg_exch2016_smtp_587 exchange02.your.domain 587
    bind serviceGroup lb_svg_exch2016_smtp_587 -monitorName tcp
    add serviceGroup lb_svg_exch2016_imap TCP
    add lb vserver lb_exch2016_vsrv_imap TCP 143
    bind lb vserver lb_exch2016_vsrv_imap lb_svg_exch2016_imap
    bind serviceGroup lb_svg_exch2016_imap exchange01.your.domain 143
    bind serviceGroup lb_svg_exch2016_imap exchange02.your.domain 143
    bind serviceGroup lb_svg_exch2016_imap -monitorName tcp
    add serviceGroup lb_svg_exch2016_smtp_465 TCP
    add lb vserver lb_exch2016_vsrv_smtp_465 TCP 465
    bind lb vserver lb_exch2016_vsrv_smtp_465 lb_svg_exch2016_smtp_465
    bind serviceGroup lb_svg_exch2016_smtp_465 exchange01.your.domain 465
    bind serviceGroup lb_svg_exch2016_smtp_465 exchange02.your.domain 465
    bind serviceGroup lb_svg_exch2016_smtp_465 -monitorName tcp

    maybe you make it same or better
    regards frank

  3. Nice post. Quick question.

    If I create a LB VIP on the NetScaler with port/protocol of */ANY to the back-end CAS servers, All of the services work fine, OWA, Active Sync, OAB, RPC, etc, all function..

    BY following the guide it breaks my outlook clients (externally) they prompt for password continuously and users cannot login.

    Any ideas?

  4. How do you configure IMAP monitor for Exchange 2013? Netscaler routes traffic to Exchange even if the server is in maintenance mode because it sees that port 993 is available. Based from packet capture, it is receiving acknowledgement from the server when it checks port 993. Once the traffic is routed to Exchange, it fails because the associated IMAP service is in maintenance mode.

  5. Hi Julian,

    great blog. Help so much.
    But I have some questions about the general structure of your topology, because I am also quite new to NetScaler.

    1. Where do you need the LB VIP According to the sketch, the internal clients alsoconnect to CS VIP?! And there is no reference to the LB VIP … should it have to be entered internally somewhere?
    2. Where do you use an external IP – mentioned in requirements? I find in your deployment only the internal CS VIP. Where and how should I set up the external address? Another CS for external or how is externel traffic redirected to internal CS VIP?

    Thank you in advance

    Greetings Kevin

    1. Hi Kevin,
      1.) The LB VIP .248 is only for load balancing IMAP/SMTP traffic. Internal Clients should connect to the internal NetScaler appliance. If you only have a NetScaler in the DMZ you can create an additional vServer without AAA authenication and create a dns record which pointing to the VIP.
      2.) For the external access you need to create a DNAT to your NetScaler CS VIP. Internal access is going directly to the Content Switch.

      1. Hey Julian,
        Thank you very much. Your explanation helped me a lot. Then I have only one more question.
        If I was slipping internal Clients, as well as external Clients via a NetScaler in the DMZ, would I create another LB vServer for each Exchange LB (SMTP, IMAP, OWA, EWS, …) without attached AAA? And would I need a second CS vServer (internal use) without AAA?
        If so, is this a possible setup?:
        > external IP via INAT to CS VIP (with AAA for external)
        – > LB VIP for SMTP and IMAP (with AAA for external)
        – > LBs for OWA, autodiscover, … (with AAA for external)
        >CS VIP (without AAA for internal)
        – > LB VIP for SMTP and IMAP (without AAA for internal)
        – > LBs for OWA, autodiscover, … (with AAA for external)
        Is this a clean and supported solution or is there some mistake?
        Or can this be done with CS policies (for internal and external clients) an the same CS forwarding to different LB VIPs?
        Thank you again 🙂
        Greetings Kevin

        1. You Need to setup vServer with and without AAA enabled. You are correct 😉
          – lb_owa_external
          – lb_owa_internal
          In big environments you normaly have an internal NetScaler pair and can just create a Service on the DMZ NS which is pointing to the internal OWA LB. Then Setup a LB vServer, specify the Service (Internal) and enable AAA.

      2. Hi Julian,
        Thank you for your answers so far. They help me a lot to get deeper into Netscaler.
        So I only need two different LB vServers (one for OWA internally without AAA and one for OWA externally with AAA).
        But what would a policy look like at CS VIP that can distinguish whether request is for internal or external OWA LB vServer?
        Or is a second CS needed just for external requests?
        Greetings Kevin

        1. Method 1 – You could create CS Policy which is filtered by the requested Hostname/URL and the Client Source IP (CLIENT.IP.SRC.IN_SUBNET(x.x.x.x/x)
          Method 2 – Create a second CS and Point internal DNS requests to this VIP

  6. Hi Julian,

    Great blog. This is far better explained and indepth than what the “official” Citrix documentation recommends.

    One question:
    In your scenario you use one IP address for the HTTP/HTTPS Content Switch and another IP address for SMTP and IMAP.
    Presumably this means that Outlook and OWA would connect to one DNS A record (e.g. and SMTP and IMAP would connect to another (e.g.

    Is it possible to use just one IP address for HTTP, HTTPS, SMTP and IMAP?

    The reason I’m asking is because there are currently around 300 servers and printers using SMTP relay to send email to a plethora of different DNS entries pointing at the old Exchange environment and it’d be quite a daunting task to update them to point at the correct DNS A record that is pointing at the SMTP/IMAP load balanced VIP.

    Kind regards

    1. Of course, you can create a Content Switch with the IP (HTTPS) and a Load-Balancing vServer using the same ip address with your SMTP/IMAP ports. Keep in mind: You can not use the same port for a single ip address.
      CS – – SSL – 443 (OWA)
      LB – – TCP – 25 (SMTP)
      LB – – TCP – 143 (IMAP)
      Not valid:
      CS – – SSL – 443 (OWA)
      LB – – TCP – 443 (SMTP)
      LB – – TCP – 143 (IMAP)

  7. Excellent article Julian!
    I am running into a little authentication issue with this setup, and I was hoping you can guide me in the right direction, we are not using any of the features highlighted in 4.7, 4.8 and 4.9. I also added an entry for the powershell virtual directory.
    Phones, OWA and ECP are working as expected but the Outlook clients (2010 and 2016 in online mode because we use Citrix lol) keep prompting for credentials and for some reason I can’t get passed that. I was able to connect once using Outlook 2010 but as soon as I closed it I was challenged with the credentials prompt again.
    Any ideas? Do we need to enable AAA?
    Thanks a lot!

    1. You don’t need AAA. It’s only for improved security implementation. Can you see a failed login attempt in the Exchange Security eventlog? Are you using NTLM or Kerberos authentication for RPC/MAPI?

      1. Thanks for getting back to me so soon.
        Unfortunately the logs already rolled, but I’ll try to catch it tonight.
        What I noticed is that the MAPI virtual directory on one of our Exchange servers is set to Ntlm,Negotiate,OAuth and the other one for some reason is set to Ntlm,Negotiate, I’m going to make sure both are set to Ntlm,Negotiate,OAuth and then try this exercise again, thanks for the tip.
        We are still in the middle of the migration so we also have some RPC connections going back to the Exchange 2010 CAS servers for Public Folder access, there is an lb vserver (*/any) going to back to the CAS servers that will decommissioned once the migration is completed, could this be a factor as well?
        Thanks again.

          1. Julian,
            I was able to bypass the Outlook authentication issue by setting the MAPI persistence to SOURCEIP as defined here:
            I definitely like your approach a lot more, but couldn’t figure out what was preventing me from logging in, I saw the header in Fiddler and that’s what made me switch the persistence.
            Any thoughts?
            And again many thanks!

  8. Hi Julian,
    Little mistake at the commands at chapter 4.8
    #Enable Front End Optimization
    enable ns feature FEO
    #Front End Optimization
    #Replace FQDN
    add feo policy feo_pol_exchange2016 ‚HTTP.REQ.HOSTNAME.CONTAINS(„“)‘ MODERATE
    bind lb vserver cs_exchange2016_ssl -policyName feo_pol_exchange2016 -priority 100
    I think you would like to bind the FEO Policy to the CS vServer, not a LB vServer, so
    bind cs vserver cs_exchange2016_ssl -policyName feo_pol_exchange2016 -priority 100
    would be correct.
    Thanks for your article, very good Job!
    Julian 😉

      1. Thanks Julian! One more question: if you activate AAA for autodiscover, will you be redirected only for first time ocnfiguration, or will this ocure more than once? can this be seen as a 2-factor auth. for outlook sync if you do not use mapioverhttp?`

        1. After you have been authenticated to the AAA Server the credentials can be used for different sevices. After you logout for example from OWA Service you Need to Login again to use AutoDiscover or ECP. It’s No 2-Factor.

  9. I’m starting to feel dumb because I have followed 3 guides like this to load balance Exchange 2016 and I can’t get it to work!

    After following all the steps in this guide I then simulate a server failure by disconnecting the NIC and everything works great at this stage but if I simulate a SERVICE failure by stopping the web service then my Outlook disconnects and I can’t use OWA/ECP anymore. Is this expected behaviour? I can see the services like owa/ecp/ews/etc as being down on the Netscaler but Outlook is disconnected and OWA/ECP in a browser doesn’t work (I get error 500 or 503). Only after starting the web service again does everything start to work again.

    Any ideas?

  10. Great walkthrough. Have this working in the lab for Exchange 2013 (had to disable the FrontEndOptimization to get to work properly will have to look into that). But other than that it works great. I do have a question.

    Not being an Exchange admin can you tell me how much different the configuration would be to support Exchange 2010?

      1. So in theory it should work as long as modify the health checks? And possibly use the „PBack“ insert method? Basically I have tried the same configuration and its not passing SSO. Everything else seems to be ok. I just disabled monitoring on the services for testing. I will keep at it. Thanks for the reply.

          1. Thank you for the article link. I had been trying both methods. It appears the rewrite is getting hits but still no SSO. I am assuming the PBack Cookie is not being passed from the AAA. I will take a NetScaler/Wireshark trace and see what it shows. Not sure exactly where to look but the plan would be to capture directly hitting OWA (which fiddler shows the PBACK) and then capture the AAA traffic once it stops on the OWA page where I don’t see PBack Cookie.

      2. Was able to get this to pass the SSO for 2010 by adding in a “Name Value Pair” and setting it to Static vs Dynamic on the SSO Profile.

  11. The MAPI LB vServer is showing as up/healthy. I did get a popup for my password when opening Outlook but after changing persistence to SOURCEIP this got Outlook to connect again so thanks!

    The next issue I keep getting is that when I stop the web service on one of the mailbox servers to simulate a service failure Outlook then disconnects and when I try to login to OWA/ECP I get a blank page? The Netscaler is correctly showing that the service group is partially down but I still can’t use Outlook/OWA/ECP. Any ideas?

  12. I guess I should first ask, if I stop the web service on one of the Exchange servers, should Outlook/OWA/ECP continue to work on the other servers?
    I’m not too familar with Wireshark so what am I looking for?
    I use the URL: and that always shows in the browsers address bar.
    I’m not using AAA (yet).
    Besides Wireshark is there anything else I can check on the Netscaler to troubleshoot this (like logs etc)?

  13. Thanks for the help!
    I tried Fiddler and it shows me: HTTP/1.1 503 Service Unavailable (I get this when I stop the web service on one of the Exchange servers)
    Which is odd because I thought the Netscaler should stop sending traffic to a service on a server when it detects that it is down (using the health monitors)?
    Whats interesting is that, if I simulate a server failure (by disconnecting the NIC from my VM) then Outlook/OWA/ECP works perfectly after the failure. It’s only if I simulate a web service failure that I get HTTP/1.1 503 Service Unavailable errors!

  14. Yes! If I stop the service on EX01 then when I browse I get a 200 OK!
    On the Netscaler I can see the service group showing as partially down.

  15. When the web service is stopped/disabled, is there anything I could be missing in the Netscaler config (monitors, lb servers etc) where you have to tell the Netscaler to NOT send traffic to services that are in a down state?

    I’m just confused as to why traffic is still being sent to a server that is in a down state?

  16. So I asked this question on the Exchange forum and basically if you have a service failure (planned or not) the cluster will not work.
    So this wasn’t a Netscaler issue but a design limitation with Exchange.

      1. What I have been wondering is, why have the healthcheck.htm page for each virtual directory if the cluster goes down with a service failure?

  17. For whatever reason my outlook clients refused to connect after redirecting my DNS records to the CS vServer. This particular environment was still using RPC for Outlook connectivity with Exchange 2016. Making the following change to the persistence on the RPC LB vServer resolved my issue. I followed BlackJack82’s recommendation and also did the same for MAPI. I am not using AAA, Front End Optimization, or Integrated Caching (4.7 – 4.9).

    add lb vserver lb_vsrv_ex2016_rpc SSL 0 -persistenceType SRCIPDESTIP
    add lb vserver lb_vsrv_ex2016_mapi SSL 0 -persistenceType SRCIPDESTIP

    Thank you for the great write-up Julian! This was exactly what I needed to get this configured. Thanks

  18. hi Julian
    this blog is so fantastic, maybe it is time for part2, “restrict smtp relay with URL pattern set file and responder policy” ? i get today this question, and when i look in Citrix Forums, there are many different ways, but i think to make a whitelist with URL pattern set and a responder policy, this will be a very good Option? what did you think about that? is it a blog what you can / want make? thx and best regards

  19. Hello Julian nice blog I have one query I want to load balance IMAPS (993) service on Citrix netscaler. I am using exchange 2013 in backend and netscaler 11.0.53 VPX. I have configured the IMAPS successfully but while configuring IMAP account in local email client (outlook) am getting CAS server local certificate warning instead of my Exchange SAN which already installed and mapped on netscaler.
    Please help it’s bit urgent.Thanks in advance.

      1. Yes certificate installed correctly on CAS as when had tried skipping Citrix loadbalancer and directly using CAS server while configuring the IMAP on local system correct SSL cert it is showing
        But when same query come from Citrix LB then it is showing CAS server local root CA

  20. hi Julian
    i want allow only a range of ip Adresses that can relay to the Exchange. i want not that everybody from Network can relaying to the smtp/Exchange. that is my Goal. and someone do it with acl what is Network, some do it with URL pattern and a whitelist file, what will be easier to handle. but i am not realy sure, what will best Option for that case.

    1. Give it a try with that pattern set whitelist regarding my knowledge and what I could find in the edocs this is for Web Traffic (http,https) only and will not work. The best option is always a matter of taste. For me this is a network demand and should be configured on the firewall. When there is a lot of change in the whitelist maybe its the better Option to go with NetScaler ACL because you dont need to ask the network team all the time to change the configuration.

  21. Thanks for the post, where you have a second site which holds e.g. two of the Exchange DAG members (4 members in total (2 in Primary/2 in DR site) A/A site how would LB work with Netscalers at a site Level please.

      1. I was load balancing them and going straight to the LB vServer, and moved over to your configuration. As soon as I moved over I have some users that now get a continuous Outlook login prompt, removing the profile and nothing works.

  22. Not much. On 2 users sitting side by side, one had a slightly higher version of Outlook 2013. Same database and same server. But then another user that had issues had that same slightly higher version as the 2 users sitting side by side.

  23. Hi Julian,

    Have all your config in place and everything seems to run fine with the exception of anything involving the 401 Authentication for Autodiscover and Activesync. The clients will continuously prompt for credentials.

    If I remove the binding for AAA on either they both work fine. The only client that seems to work with 401 AAA is Outlook 2016, though majority of clients in environment is Outlook 2013. Our NS is version 12.x

    I checked the Authentication LDAP logs and it is accepting the credentials from what I can see. Any ideas?

      1. Hi Julian,

        I was able to resolve by putting in the following config and binding the policy to both my autodiscover and activesync loadbalancing VIPs:

        add tm trafficAction SSO_Profile -SSO ON -persistentCookie OFF -InitiateLogout OFF
        add tm trafficPolicy SSO true SSO_Profile

  24. Julian,

    I was wondering if you had a recommendation for the timeout value of the MAPI lb_vsrv; for RPC it is set to 30 minutes so I have started with using that, but has anyone found that to be too short or too long? What are people using for the timeout for MAPI with SOURCEIP persistence?

    add lb vserver lb_vsrv_ex2016_mapi SSL 0 -persistenceType RULE -rule ‘HTTP.REQ.HEADER(“Authorization”)’ -timeout 240

    add lb vserver lb_vsrv_ex2016_mapi SSL 0 -persistenceType SOURCEIP -timeout 30

    ### As a note, maybe you should update the blog post to replace the persistence to SOURCEIP in general to keep the config up to date with all that’s been learned.

    Also, just wanted to THANK YOU for putting this blog post together. This is by far the most comprehensive write up on configuring LB of Exchange 2016 I have found. It is extremely useful.

    1. After rethinking I have changed the MAPI timeout to 240 to match what you had recommended for the service when using RULE persistence. I assume that in itself answers the question, but if you have anything to add please let me know.

      add lb vserver lb_vsrv_ex2016_mapi SSL 0 -persistenceType SOURCEIP -timeout 240

      1. Thank you for the quick reply. As I am interpreting it, so long as the LB_VS timeout is longer than the keepalive interval than everything should be good. In that case assuming the TCP keepalive is setup to 15-20 min, than 30 min timeout would be fine. It also then should be the same that keeping it as a 240 min timeout wouldn’t hurt either. I actually left the timeouts as 240 mins to match the service timeout values you had indicated while they were setup as RULE instead of SOURCEIP and so far so good. I have left Outlook clients with both 2010 mailboxes access via 2016 Exchange NetScaler CS VIP / 2016 Exch Servers Proxy and Outlook clients accessing 2016 mailboxes via the CS VIP and haven’t had any issues with the connectivity timing out, disconnecting, or continually prompting for credentials. All 3 of those issues were seen while using the RULE persistence so from what my testing is showing I think everything is now working as it should be without issue with SOURCEIP -timeout 240 for RPC and MAPI.

        If I am misunderstanding that timeout setting and you believe I should change it down to 30 from 240 for some reason please let me know. Otherwise I appreciate the work done and sense of community you have on this topic and wish you a great day!

        1. You interpreted correctly. Doesn‘t matter if the LB vServer is configured for 30 or 240 minutes timeout. The value configured on the Exchange server will win. Thanks for your feedback. Appreciate it. Wish you a nice weekend 🙂

  25. Thank you for such a great setup guide. We have a slightly different scenario: Netscaler VIP in the DMZ with similar settings as the above, that then points the authenticated traffic in to the internal Netscaler VIP that handles the load balancing for internal clients to the exchange servers. This setup seems to work fine for Exchange 2010 as it replaced our TMG setup a couple months ago. But now that we’re trying to get it to start using our 2016 servers, it runs into multiple issues. Anything from double logins (once for AAA, and once for Exchange OWA), to not being able to get logged into a 2010 mailbox, but it works with a 2016 mailbox, to just going to a blank page. This also seems to differ based on browser used. Safari and Chrome work mostly as expected though sometimes double logins on each, Firefox always has double logins or just a blank page, and IE is all of the above. And it seems everyone’s setup guide basically has a single netscaler (or HA pair) with 2 vips (1 for AAA and the main vip) that connects directly to AD for authentication and then load balances to any of the exchange 2016 servers.

    Any ideas are greatly appreciated, we’ve been banging our heads against the wall for about a month now with 3 failed attempts at cutting over. Thanks!

    1. Without AAA everything is working? I configured a NetScaler (Exchange 2010) the day before yesterday with the same commands (excpect the monitors and AAA) –> no problems. I changed the persistence for the MAPI/RPC vServer from RULE to SOURCEIP last week. The RULE expression was somehow denying the authentication for the services. You always got a credential prompt. Do you have this already implemented?
      When using Exchange 2010 your SSO Form action needs to be configured a little bit different.
      If you are using a NetScaler in the DMZ & LAN:
      – Create OWA/MAPI services on the DMZ NetScaler (LB VIPs from the LAN NS)
      – Create LB vServer with this services (DMZ)
      – Configure AAA for the LB vServer (DMZ)

      P.S: For testing the OWA SSO just edit your local host file. The webmail URL should resolve to the CS VIP.


      1. The current setup is DMZ netscaler with AAA for pre-auth, that points to the LAN netscaler for load balancing. The LAN netscaler only has the 2010 CAS servers. This is working.

        The new setup (and our test VIPs) is DMZ netscaler with AAA for pre-auth that points to the LAN netscaler for load balancing. the LAN netscaler new test VIP just points to the new Exchange 2016 servers.

        So would we set up the above all on the DMZ netscalers, and have those still point to the LAN netscaler VIP, and should that LAN vip be just load balancing, or should it also have the same setup as above?

        We’re also tossing around the idea to have the DMZ netscaler just go directly to the exchange 2016 servers. Essentially have the setup you describe on both the DMZ netscaler and the LAN netscaler, but have each set of netscalers go directly to the exchange 2016 servers, instead of having the DMZ netscaler point to the LAN netscaler vip.

        Thanks again for your help and blog post!

  26. Excellent write up on the Citrix side of things! I am curious what if any action I need to take with Exchange send or receive connectors to make this work. Or the URLs for the virtual directories? You must need to do *something*
    Thanks in advance kind sir!

    1. There is no change at all on the send/receive connector or virtual directories. OWA is configured for FBA (default setting) and your internal and external urls depends on your environment. If there is something unclear feel free to ask.

      1. Thank you for the quick reply! In the process of writing a reply to clarify my question, I answered it myself. I was getting hung up on the NetScaler’s role in all of this, and over complicated it. The send and receive connectors only manage SMTP flow, which we are doing simple LB on, so I don’t have to worry about Exchange’s mail-flow there. I’m good now! Thanks again!

  27. Hi Julian excellent blog I have not seen any blog thats better than this one.I just had a small question to you regarding Exchange running on 2 sites with mpx netscalers 8005 enterprise edition on both sites in that setup what is the best way to get HA in case i loose the entire sites as from exchange 2016 dag perspective i have active database on one site and passive on another site and a lagged on the active site issues that i have is if one site goes down my mails stop working. I was wondering if i can have a quick chat with you through email and get some opinion from you.cheers Jack

  28. Thanks very much for compiling all this information; it was quite helpful.
    One point that might be of interest.. I’ve noticed URLs like GET /owa/prem/15.1.1466.8/resources/images/0/ewsprite1.mouse.css which would potentially match both CONTAINS(„/ews“) and CONTAINS(„/owa“), which makes the CS policy binding priority important (though I notice you have /owa first, presumably for this reason).
    I chose to use HTTP.REQ.URL.PATH.SET_TEXT_MODE(IGNORECASE).STARTSWITH to match the IIS virtual applications (/Autodiscover /EWS etc). It also might be a less costly comparison than CONTAINS.
    Also, it seems that CONTAINS(“Microsoft”) might properly be replaced with STARTSWITH(„/Microsoft-Server-ActiveSync“). I realize that one came from Citrix documentation.

  29. Hello,
    Thank you for the fantastic blog post!
    I have a little issue, I followed the instructions but after a successful authentication via hostname, the AAA server displays the following error: Target URL not found for redirect after successful login. Please contact your administrator.
    Any idea how to redirect this to OWA?
    Thank you,

    1. Are you accesing the CS/LB VIP or the AAA server directly? Normaly you get this message when the NSC_TASS cookie is missing on your client. This happens if you browse to the AAA server and login. It’s only working from the LB/CS (Redirection).

      1. Hello,

        Thank you for the quick reply!

        I changed the priority of the command from 90 to 105, and the cookie appeared:
        bind cs vserver cs_exchange2016_ssl -policyName cs_pol_aaa -priority 90

        Thank you again!

    2. Beautiful blog post, Julian!! thank you so very much. ran into the issue just as Ryan.
      I had the same issue. “Target URL not found for redirect after successful login. Please contact your administrator.”
      changed the policy binding priority to 105. and it works.
      however, it only works when i enter and auto Redirects to
      if i enter directly the issue persists. and goes back to target URL not found for redirect after successful login”
      Wondering what i should be doing to fix the Https.

  30. Hi Julian,
    I have the same issue as Ryan. Note that I did copy&paste (changed values to match my domain) of your commands up to 4.7 as 4.8 and beyond and additional functionality which I will continue later.

    url entered in the browser:

    Here is an optput of the ns.log

    Jul 2 09:58:12 07/02/2018:06:58:12 GMT ns-int-1 0-PPE-2 : default AAA Message 71637 0 : „In update_aaa_cntr: Succeeded policy for user testSSO = LDAP_SAM“
    Jul 2 09:58:12 07/02/2018:06:58:12 GMT ns-int-1 0-PPE-2 : default SSLVPN Message 71638 0 : „get_session aaa_info flags 91 flags2 0, new webview 0, sess flags2 21, flags3 0 “
    Jul 2 09:58:12 07/02/2018:06:58:12 GMT ns-int-1 0-PPE-2 : default AAATM LOGIN 71639 0 : Context testsso@ – SessionId: 27- User testsso – Client_ip – Nat_ip „Mapped Ip“ – Vserver – Browser_type „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.171“ – Group(s) „N/A“
    Jul 2 09:58:12 07/02/2018:06:58:12 GMT ns-int-1 0-PPE-2 : default AAATM Message 71640 0 : „AAATM Login: created session for with cookie: “
    Jul 2 09:58:12 07/02/2018:06:58:12 GMT ns-int-1 0-PPE-2 : default AAATM Message 71641 0 : „AAATM: LOGIN: invalid redirect url ▒▒^Z“
    Jul 2 09:58:12 07/02/2018:06:58:12 GMT ns-int-1 0-PPE-2 : default SSLVPN Message 71642 0 : „AAA Client Handler: Found extended error code 262157, ReqType 16388 request /cgi/login, cookie hdr _ga=GA1.2.1957678141.1529053026; NSC_TASS=/owa“

    1. Can you check your “Action URL” in the form sso profile? Should be “/owa/auth.owa”.
      Are both traffic policies bound to the OWA LB?
      Is it working without the cs policy “cs_pol_owa_redirect”?

  31. seemes tha this name needed to be different add cs policy cs_pol_aaa -rule ‘HTTP.REQ.HOSTNAME.EQ(“”)’ -action cs_act_aaa
    I had it point to the same url as the mail server. for both instead of for owa/ecp and for the authentication server.

  32. We are using the (/xxx/healthcheck.htm) monitors for LB our Exchange 2016 services. I need to disable TLS 1.0 on our Exchange servers for PCI compliance but when I do the healthcheck.htm monitors fail the handshake. When will these work with TLS 1.1 or 1.2.? Or is there a different monitor you recommend that works with TLS 1.2?

  33. If you follow this guide and use the AAA feature does that mean that ALL of the traffic and requests go to the AAA server first?
    It seems like with the AAA enables the free-busy and calendars do not work….

  34. I am not a master of Net Scalers but i know Exchange and was asked if we could block everything except activesync and of course mailflow externally. No EWS,, No ECP, no OWA. Internally yes but no external access on those.

    There are 5 exchange servers load balanced with Netscaler.

    I know you can block do this with an F5 and there is a messy way to do this with Kemp but since I am not fully aware of the Netscalar capabilities I thought I would ask in here.

  35. Hi Julian,
    Thank you so much for this guide it was really helpful and worked like a charm.
    I have Exchange 2013 and the AAA feature active without group filtering.
    The only problem that i have is that the external outlook doesn’t work. I see in the exchange security logs audit failures which say unknown username and password.
    We have ntlm active on outlookAnywhere for internal and external clients. Am I correct that this setup only works when i have basic active as externalauthentification method?
    Login to owa works fine with the same credentials / user / endclient.

    Thank you so much for your help and guide 🙂

      1. Hi Julian,
        I finally was able to look into it and made it working. The article above was so confusing, here is my attempt in explaining it.
        I tried to adopt your naming of the actions/policies so that it is easier to understand.

        1. Create an AD Account in the Active directory for the KCD and set the spns for your CAS Servers (or MBX if you ran 2016, my customer has 2013)
        My account is named KCD
        I have
        setspn -A http/ CONTOSO\kcd
        setspn -A host/ CONTOSO\kcd
        setspn -A host/ CONTOSO\kcd
        setspn -A http/ CONTOSO\kcd
        setspn -A host/ CONTOSO\kcd
        setspn -A http/ CONTOSO\kcd
        Now on the KCD user in AD an new tab “Delegation” is visible and you need to add all of your CAS Servers (or MBX in 2016) with HOST and http
        As seen here (but he forgot the HOST service type)

        2. Verify that on the CAS Server, in the mapi subsite in IIS, under authentication option , under windows authentication, the NTLM Provider is added (is done by default when you enable ntlm on mapi VD, but good to know/check)
        3. on the netscaler:
        # Add Negotiate authentication policy and action
        add authentication negotiateAction negotiate_act_EXC_KCD -domain -domainUser kcd -domainUserPasswd ****** -NTLMPath “”
        add authentication negotiatePolicy negotiate_pol_EXC_KCD ns_true negotiate_act_EXC_KCD

        # Create the previously kerberos account and session policy for SSO
        add aaa kcdAccount -realmStr -delegatedUser kcd -kcdPassword ******** -userRealm
        add tm sessionAction tm_act_exchange2013_KCD_sso -SSO ON -ssoDomain ‘’ -kcdAccount -defaultAuthorization ALLOW
        add tm sessionPolicy tm_pol_exchange2013_KCD_sso ns_true tm_act_exchange2013_KCD_sso

        # Create a new AAA vserver that uses KCD and bind the wildcard cert
        add authentication vserver AAA_Exchange_2013_KCD SSL -AuthenticationDomain
        bind ssl vserver AAA_Exchange_2013_KCD -certkeyName ‘Wildcard-Flashmob’

        # bind the negotiate and SSO policies to the new AAA Server
        bind authentication vserver AAA_Exchange_2013_KCD -policy negotiate_pol_EXC_KCD -priority 100
        bind authentication vserver AAA_Exchange_2013_KCD -policy tm_pol_exchange2013_KCD_sso -priority 100

        # bind the new AAA Server to the Load balancers that need KCD
        set lb vserver lb_vsrv_ex2013_mapi -authnVsName AAA_Exchange_2013_KCD
        set lb vserver lb_vsrv_ex2013_rpc -authnVsName AAA_Exchange_2013_KCD
        set lb vserver lb_vsrv_ex2013_autodiscover -authnVsName AAA_Exchange_2013_KCD


        Let me know if this helps

        1. Hello Kim,

          thanks for the feedback.
          I think you can make the setup even more simple. Just create a kdc account with the specific realm and bind it to the aaa action. I assume the login is happening with username and password. Otherwise kerberos impersonation is not working.

  36. Hi Julian,

    Thanks for a great article.

    I set up Exchange 2010 access via a Netscaler but only using Standard license features. Everything works as expected, except when Exchange tries to proxy the connection between two CAS servers. When logging into OWA, the error “Exception message: The proxy CAS failed to authenticate to the second CAS (it returned a 401)” is returned, which does not happen if I bypass the Netscaler.

    The errors in Exchange point to a Kerberos issue but I’m not really sure where to go from here. If you have any ideas on how to solve this, that would be much appreciated.


  37. Jullian,
    In section 3.1 you noted: “If you dont load balance DNS/LDAPS/NTP the traffic will flow from the NSIP. In my setup the servers are load balanced –> The SNIP is communicating with the backend servers.” Are you saying that you must create a LB VIP for DSN/LDAPS/NTP? My DNS and NTP are set in the appliance configuration section on the Load Balancing section.

    1. You don’t need to load balance DNS and LDAP but why you shouldn’t when you have the ability to do it? 🙂 In some cases maybe it’s even necessary to source the DNS/LDAP traffic by your SNIP because the NSIP is only used for management traffic (SSH/WebGUI)

  38. Hi Julian,

    Very nice and extensive article 🙂 I followed the steps in the Article, however after Logging in on my AAA Server I get stuck in a “loop” where the page keeps reloading and the Log in /var/log/ns.log keeps giving the following message:

    FORMSSO: POST: NVPAIRS: name passwordText has no value, not copying
    FORMSSO: Could not find form in the response buffer of size 60000

    The authentication on the AAA Server is successful, but it looks like the redirect is going wrong. When I stop the browser, and open the Site again I can login on OWA. Any ideas?

          1. I tried several different browsers (Chrome, Edge, Safari) and different computers but all show the same behaviour. The A Record for webmail.**.com and authenticatie.**.com both point to the same VS IP. Did I make a mistake with that maybe?

          2. You can use the same VIP when it’s a CS which is redirecting the traffic to the correct AAA/LB vServers. Looks like there is no problem with the traffic profile/SSO profile because you get the authorization cookie and single sign on is working. Can you remove any rewrite/redirect policies which is associated with the CS and the OWA LB vServer?

  39. Hi Julian,

    Awesome blog. I am experiencing problem in configuring a email connector for our mail box to configure IMAP, so that this cloud based application will fetch the email from this email box and raise a ticket against each email.

    Exchange is currently load balanced using Netscaler. Now I need to configure IMAP over SSL (993). I have done below steps.

    On our firewall, I have created a NAT rule to send traffic to Netscaler LBVS VIP.
    Created service group in Netscaler and binded exchange servers using port 993TCP and assigned the TCP monitor.
    Created LBVS VIP and bind the service group to the LBVS.
    Now the netscaler is listening to 993 from exchange boxed as I can see all service is UP and GREEN.
    Note : Since it is TCP port i couldn’t bind any SSL certs at netscaler level.
    Testing that I have done – Telnet the hostname with 993 failed externally.
    Telnet to the local netscaler LBVS VIP from exchange box on 993 port connecting.
    Telnet to the local netscaler LBVS VIP from netscaler appliance SSH on 993 port is connecting.

    I am not sure what I am missing.Should we require the MAPI content switching config also to be in place to make this work?

    Your help is much appreciated.!


      1. HI Julian,

        From LAN IMAP LBVS is accessible, however apart from exchange box and netscaler I can’t telnet 993 even from lan machines.. I am not sure what I am missing. here.

        Already I have the direct NAT of public IP to LB VIP.

        As of now, I don’t have any MAPI configurations in place. This is my earler question whether I need MAPI configuration to make this work. you have cleared it now in your reply saying not required.


  40. Firewall is at DMZ. Can you please confirm the below configuration made is as per standards?

    Created service group in Netscaler and binded exchange servers using port 993-TCP and assigned the TCP monitor.
    Created LBVS VIP and bind the service group to the LBVS.

    Sorry for the confusion. I have checked in other LAN machines. I can telnet to port 993 internally to the LBVS VIP.
    It is only not working from externally. I have made necessary changes in the Firewall, still not working.

    Any ideas


    1. Yes but I would create a more specific monitor. You can poll for the receive string. It’s like „IMAP Exchange Service is running..“ You can see the exact message via telnet. If it’s not working from external I suggest there is a problem with your NAT. Can you create the DNAT directly to your Exchange for testing?

  41. Hello, thank you for this awesome guide!
    We have a problem that the user is prompted to enter his password after he switches from one network to another. (LAN to WiFi)
    Is this made by design (session persistence sourceip) or is there any way to avoid those outlook prompts.
    Thanks in advance.
    Best regards,

  42. Hi,
    Thanks for a great article, stumbled upon a small problem. I am not able to catch the /owa/logoff.owa since its never sent. (verified with sniffer). Using Exchange 2016.
    Do you know if there is a solution to this

    1. @SLR – I am dealing with the same issue. I can’t get the force logoff or the cookie cleared and am not finding any solutions or alternatives. I am wondering if Exchange is sending a URL back to the client but it never reaches the Netscaler because we don’t have 80 allowed on the firewall. Traces ahead….

  43. hey Citrix guy!

    I noticed that you set up an LB server for SMTP services. was this set up using SourceIP? I’m just curious if you have set up SMTP sourceIP LB using different subnets (NS in one subnet, exchange servers in another subnet). I’ve been asked to do this and although I have set up sourceIP LB for exchange on the same subnet as the NS, I have not done so when there are 2 subnets. I’m thinking it may not be possible but thought I would check anyway.

    1. Hello Paul the thing with SourceIP persistence is that its working without any problems for an internal client. If we take a look at the external client access which is happening over a DNAT (in most of the cases) the backend server load could be very high because its always coming from the same source IP. I would go with NONE persistence for SMTP. But I am not an Exchange/SMTP guru 🙂

  44. Hello,
    Thank you for the guide. Do you have a blog on restricting access to SMTP Traffic. Currently in the configuration you have and I have implemented, any device that knows the relay VIP can now send traffic through the relay. I would like to restrict by IP as you can in the Exchange Relay setting in Exchange ECP.

  45. Luke E. – If you want to restrict allowed relays / senders then you need to add ACLs. What I have done previously is add ACLs for individual IP addresses or networks with a priority of 1-100 or whatever number you need and then add a blanket DENY ACL and give it a very high priority number like 5000. If you have a lot of IPs to add you can use CONCANTENATE in excel to help build your commands and use Get-ReceiveConnector -Identity “Mail Relay” | select-object Identity,RemoteIPRanges to dump the allowed relays on your existing relay connector in Exchange. The only alternative would be to route your mail relays direct to a secondary IP bound on an Exchange Server NIC – but no HA. You can view your configured ACLs at any time by running show ns acl.

    1. If you do not want to work with ACLs this should be possible with a listen policy on the LB vServer as well.

  46. I can´t see avalible any https VS, looking in the owa VS, service groups members monitors; I get the Failure – Time out during SSL handshake stage error

  47. Hello

    Could you clarify why do you use SSL-based LB vServers ( behind CS vServer instead of HTTP ones ? At the first look HTTP will be enough because these servers are not directly accessible outside ADC and all communications are only between CS and LB one. So additional ADC resources will be used for encrypting/decrypting the stream between them if SSL is used.
    Or I miss something?

    Thanks in Advance

  48. Hey Julian,

    Perfect Blog articel, Thank you alot.

    I have one question.
    You configure a session action and policy for the SSO.
    Ist it just me and i havent found it, or ist this policy not bound to the AAA Server?

    BR Christian

  49. The OWA redirect for default server is wrong and potentially dangerous.
    Undefinded URLs/content switches will be passed through to the backend server(s), because its basically a /* which negates all the other content switches.

    For example, if /activesync or /mapi is not configured. This particular redirect will execute the owa action and this will simply pass the transaction to the servicegroup.

    I suppose the problem with this lies in the concept of the netscaler. In its basic form its only a loadbalancer, with enterprise or platinum it also becomes an AAA solution, whereas with AAA you can add restriction with it.

    if you don’t have access to AAA features and want to use the redirect to owa. You would at least need to explicitly deny all the valid content switches you don’t want allow through. Like /mapi /ecp /activesync /rpc etc…

  50. Good afternoon, I have a question about it, can different versions of MS Exchange coexist in Balancing, for example 2013 and 2019?

  51. All,

    Great Article!

    Recently I load balance exchange 2019, as per details it this topic which works perfect until I attach cache policy, which makes owa inaccessible, basically keeps asking credentials but once removed all works fine. I would appreciate any suggestions.


  52. Hi guys,
    Thanks for the great article. Everything worked as expected, but we are facing a really strange problem. If we enable AAA for MAPI or EWS, users will not be able to send a message with an attachment. Without an attachment the mail flow works fine. As soon as I remove the AAA, sending a message with an attachment works again. Is this a known problem with NS version 13?
    Thank you in advance for your help and best regards,

      1. Hello guys,
        there is a fix for the mentioned problem.
        Please check the updated post with the information from Julian Jakob.

  53. Hi Julian,
    Thanks for your great article! Based upon it we are configuring this for Exchange 2013. We keep struggling with RPC. It produces a Http/1.1 Internal Server Error 43550. We currently use ADC 13.0 67.39 for our test setup.

    Does this ring a bell?

    1. Hello Joost. Is AAA in play?
      Is it working without AAA? I think for Exchange 2013 you need to have a slightly different form sso profile.

      1. Totally missed you reply, sorry about that.

        AAA is in play. It looks like a problem between the ADC and Exchange. After a case with Citrix and a consultant we decided to disable authentication for RPC as we are switching to MAPI.

  54. would you please describe more about Authentication FQDN in Virtual server?
    Which server it should be pointed to, It cannot refer me to OWA webpage

  55. I have a problem with AAA, what is Authentication FQDN role play, and what should I set there?
    Isn’t it needed to set IP address for Authentication Virtual Server?

  56. If I use GSLB between 2 datacenters, I have to create separate GSLB vServers for SSL & TCP. And I bind webmail domain to SSL vServer and mailrelay domain to TCP vServer. Will this impact other components – IMAP/POP3? They should use webmail DNS, I guess.

  57. I am having issues with autodiscover.
    Not sure how its supposed to work. My OWA SSO setup works perfectly fine.
    On my autodiscover VS, when i remove the auth, I get prompted for auth from server and even after adding credentials it keeps on prompting(loops).
    When I add 401 form basd auth profile, its the same behaviour.
    I tried to add the traffic policy to auto discover VS,as mentioned in one of the comments above but still no luck.
    Is anyone having this similar issue?


  58. Hi There,
    Looking at your article and it has raised a question around whether you could integrate Azure AD MFA with this as well? To provide MFA support for Exchange OWA, as you would only want it on OWA not ActiveSync etc.

    1. Hello Charlie. Yes this will work. But it depends with the integration of Azure MFA. If you go the SAML way with Conditional Access and Azure is your IDP you need a way to authenticate to the exchange server. The easiest way would be to use the Azure NPS extension then you already have the password of the user.

  59. Hi Julian
    I would like to do an internal LB and CS only. Can I not use the same setup and connect the internal Outlook clients to the SMTP LB IP? Or what is the different?

    1. Hi Roland. It’s the same setup. Regarding SMTP: Maybe you want to see the real client ip on the exchange server (relay). If this is needed you need to configure USIP/DSR mode.

  60. Hi Julian
    Thank you for your reply!

    I have an customer with an bad setup.
    And I want to do an parallel setup and when tested a traffic switchover .
    I have a lot of experience in other LB products but not in ADC.
    And I would like to ask you if you see any problems here?

  61. Hi mate, thanks for the article. I have followed this article to set up the reverse proxy for our exchange 2013 with AAA pre-auth. The owa/ecp MFA+pre auth on the Citrix landing page works perfectly. The apple native mail client on iPhone works without any issue. However, the Microsoft outlook app downloaded from the app store will not work with the pre-auth for active sync. it keeps complaining about incorrect email addresses or credentials. if I take the aaa pre-auth off from the lb, it will work again. Any idea. Your help will be highly appreciated.

    1. Hi David,

      on my Setup it works with native MS Outlook iOS App configured with my onprem Exchange 2016 server with adc aaa for preauth for active sync without any issues. Check if you have enabled the Advanced settings when adding your email account as you have to Setup your AD domain and your public exchange server fqdn.

      Best Regards

  62. Hi
    There seems to be a problem with the integrated caching and/or FEO in Version 13.0 (79.64). It breaks OWA. When you switch it off, it works again.
    mapi is still broken, even when you switch off the AAA Server, Outlook keeps me asking for the password.
    EWS and other services are working fine. (With AAA)
    Anybody else is having the same issue?
    Any hint will. be appreciated


  63. I have had 3 Exchange 2013 servers LB with CS supporting Outlook, OWA & ActiveSync with a single VIP and it works perfectly. Even with 2FA.
    Now, I am migrating to O365 and need to add SMTP and EWS only for O365 servers for the hybrid connector (HCW). Your article above has so many separate VIPs and services, my config is much simpler. How can I add the services I need without breaking production?

  64. Hi!
    Thank you very much and congratulations for this guide! Works perfectly with Exchange 2019 & NetScaler/ADC-VPX 13. What I also needed was the SSO-traffic-policy, as Robert commented on May 16, 2018. Otherwise, I always had an authentication error with Mapi.

    What bothers me now is the “Authn”-Type in the connection status in Outlook (right click with CTRL key on the Outlook icon). Because it says “Clear*”. What does that mean? Did I forget something?

    1. What I also needed was the SSO-traffic-policy, as Robert commented on May 16, 2018. Otherwise, I always had an authentication error with Mapi.

      add tm trafficAction SSO_Profile -SSO ON -persistentCookie OFF -InitiateLogout OFF
      add tm trafficPolicy SSO true SSO_Profile

  65. Thank you for posting this guide. When upgrading from exchange 2016 to exchange 2019, would this same guide work fine? Are there additional steps with Exchange 2019 that need to be taken? Thank you!

  66. Hi and thanks for very good guide. I was able to make it work without any problems..

    It was working perfectly, just some time ago it breaks. After authentification on AAA and redirection to exchange, I just get white page keep blinking and redirecting at “”

    Anyone one experiencing the issue? Any ideas?


  67. Hi Julian,

    I stumbled over your great blog searching for ‘Loadbalancing SMTP Port 25 with Netscaler’.

    Sorry, my question is not Exchange-specific but I need a working solution for the following problem and I hope, you can give some hints. If you think, this is not the right place for my question, feel free to delete it …:

    I want to use the Netscaler as a loadbalancer for two spamfilter agents in front of our Exchange server. A loadbalancer created by me ‘the usual way’ works fine, BUT: the spamfilter servers only ‘see’ the Netscaler’s SIP. And this is not helpful for some of the filter modules (for example: host reputation etc.) because they need to ‘see’ the original sender’s/mailhost’s ip-address. I came aware of an option called ‘Use client ip’/’Use source ip’ and activated it in the Netscaler’s server-group settings. But as soon as I do it, no traffic hits the systems any more.

    The Citrix documentation is not very helpful and more confusing than clarifying anything.

    Asking Citrix support for help, lead to nothing until today.

    If you have any ideas, I would appreciate to read from you. If not, I apologize for bothering you.

    However, thanks


    1. Hi Rolf if you want to work with USIP-Mode you need to change the default gateway of the backend server to a ADC owned IP. In this case the Subnet IP. Otherwise this will not work.

  68. Hi Julian,

    thanks for looking into my request.

    I have no experience in using the Netscaler as gateway, so: will all other queries (DNS for name resolution, https-traffic to the Internet and and and work as normal or have I to do addirional settings/services on the Netscaler?

    Thanks again,


    1. Everything will get routed through the ADC. Make sure you have enough bandwith on the VPX/MPX. Another more easy approach would be to go with SNIP Mode and work with Network ACLs or a Listen Policy Expression on the SMTP vServer.

  69. Hi Julian,

    we followed your instructions described in the above superb article!

    Unfortunately we are facing some issues with our ADC/Exchange setup – authentication for autodiscover and RPC is not working. The Remote Connectivity Analyzer shows errors like you described in this Citrix forum post:

    So my question is if you could find an answer what was wrong in your config back then? It seems that I can’t find any suitable info on the internet how to fix this issue…

    So thanks a lot for your work and maybe you could give me a small hint 🙂

      1. Thanks a lot for the answer!

        I guess you’re talking about disabling AAA for RPC/MAPI? So yes, currently AAA is disabled for this and everything is working fine.

        For Autodiscover it is still enabled but as mentioned the Remote Connectivity Analyser throws out the error.

        Could you please specify the ADAL info a bit :-)?

  70. Hi,
    Thanks first for the grat job!

    For me everthing is working fine, also AAA ActiveSync with iOS and Android and the buildin mail clients. But if the user use the Outlook app, it does not work. Sometimes the user is locked, mostly it happens nothing, so no mail is coming in. If I remove the 401 Auth from LB-Activesync, it works fine again, but we would to use AAA also on activesync. Any Idea how to solve?

Leave a Reply

Your email address will not be published. Required fields are marked *