Exchange 2016 DNS Round Robin vs NetScaler
Posted on 2016-10-06
Since Exchange 2016 no longer support CAS Arrays and everything is on the mailbox server, and users connect to the client access service on the mailbox server hosting the active DB for the user mailbox, is there a reason to logically use a netscaler for load balancing Exchange 2016 as opposed to using DNS Round Robin? If so what is the reason for using either in your professional opinions. I will still use the single name space. Any suggestions and opinions are appreciated.