Theoretically, in 2016 you don't need a separate load-balancer, DNS round-robin is sufficient.
In the real world, most companies aren't large enough for that to work out well. Kemp Technologies has a nice VM-based load balancer. They even offer one for free. You may find the free one is good-enough for you. ObDisclaimer: Kemp employs several Microsoft MVPs whom I know and trust. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Kennedy, Jim Sent: Wednesday, March 29, 2017 10:59 AM To: 'exchange@lists.myitforum.com' Subject: [Exchange] 2016 design help needed. Finally going to upgrade our 2010 Exchange to 2016. Current info: 1 CAS/Hub Transport. That is behind a reverse IIS proxy for external web mail. 2 Mailbox servers. 500 mailboxes per server. In rough numbers about half my users are OWA and half our Outlook. ActiveSync is pretty widely used. With the above setup load balancing was primitive but effective. And that is where I am not getting it with 2016. Am I looking at a separate load balancer with a VIP in front of the two servers I will now have? And if so, any suggestions on a decent unit that fits my rather small environment? A software unit that I can drop on a server would be neat since I have the hardware already.
