Microsoft Exchange Application Delivery Controller

Exchange Server deployments benefit when a load balancing Application Delivery Controller is included in the infrastructure hosting the solution. In fact, with the release of Exchange Server 2016, Microsoft’s reference infrastructure includes a Layer 7 load balancer. It’s not possible with Exchange Server 2016 to use Network Load Balancing to deliver all the services that Exchange provides to client devices.

Most rollouts of new versions of Exchange Server are gradual. The new release may have to coexist with the currently deployed version and possibly previous releases. If an organization is already running Exchange Server 2013 behind an Application Delivery Controller, such as a KEMP LoadMaster for example, then they can introduce Exchange Server 2016 mailbox servers directly into the load balanced pool alongside existing Exchange 2013 servers. Mailboxes can then be migrated over to the new release in a controlled manner. There is no need to set up a separate infrastructure as was the case in the past. If you are running Exchange 2010 then it can coexist with the new version in exactly the same way as Exchange 2013 does. An application delivery controller makes this easier to do by helping deliver a single namespace across all three versions. This means that it is possible to have the three latest releases in the same deployment, with Application Delivery Controllers helping them to coexist as well as providing all the other benefits associated with a load balancer. Such as:

• Layer 7 Application & Content Inspection based load balancing
• Layer 4 Transport layer based load balancing
• Geolocation based load balancing
• OWA and EAS service Load Balancing
• Server health monitoring
• WAN Acceleration
• SNORT based Intrusion Prevention
• User Pre-authentication and Policy enforcement based on Active Directory
• Single Sign-on support
• Dual Factor authentication support
• Real Time network monitoring
• SSL inspection
SSL Offloading
Reverse Proxy
• Protection against OWASP Top 10 vulnerabilities