Kemp LoadMaster Reviews

We use the Kemp Loadmaster to load-balance enterprise-wide applications that require high-availability. We also wanted to make sure the performance and throughput meet the needs of the usage of our applications.

These applications include Microsoft Exchange, Microsoft Active Directory Federation Services (ADFS), Microsoft SharePoint (2010, 2013), file sharing servers, multiple public-facing websites, multiple internal websites, on-premise IT Service Management applications, and others.

The LoadMaster handles both production and development environments for these applications.

The Kemp LoadMaster was very easy to deploy and we initially deployed without needing much tech support help. The management is very intuitive and can easily be used by techs without needing extensive training to use.

The LoadMaster met all of the features and performance we were looking for at a very affordable price. We were also looking to lessen the real estate rack space in our data centers and really wanted a virtual solution that will work with our Hyper-V environment.

Having a Hyper-V image that we easily deployed to multiple Hyper-V clusters allowed us to achieve high availability with the LoadMaster.

My primary use case of this solution is as a web application firewall.

Kemp mitigated our cross-scripting vulnerabilities, cookie-related issues, and content security policy issues. Instead of working on each application, we can do everything with Kemp. In addition, using Kemp has raised our site score from average to fully-secured.

I use Kemp LoadMaster for the application delivery controller. I have a couple of applications hosted behind the load balancer.

If I have an application behind the load balancer, the distribution of traffic helps me.

We use LoadMaster for HA Clustered Pair Load Balancer for primarily Exchange on-premises deployment and all supporting services (SMTP, ActiveSync, Autodiscovery, OWA/EWS, etc.)  Secondarily, for non-Exchange, application-server-based mail routing.

We implemented in 2014 as a dedicated load handling solution for inbound on-prem internal Exchange SMTP. We soon adapted the appliances to handle more tasks such as VIP-based routing to our middleware MTAs, mobile devices via ActiveSync, Outlook Autodiscover services Exchange Web Services & Outlook Web Access.

It has greatly fortified the performance and uptime of our front-door email ingress, simplified and segmented mail routing, and reduced admin overhead for mail issue resolution and troubleshooting.

The ease of the UI has allowed several relatively untrained admins to take over administrative duties, firmware upgrades, service monitoring, issue troubleshooting, and basic maintenance tasks like failover/failbacks.

It has also given us previously lacking visibility into mail flow metrics, service-based volume, connection issue granularity, and high availability.

I use Kemp LoadMaster in my company as a replacement for Microsoft Forefront Threat Management Gateway and as a load balancer for Microsoft Exchange services in an on-premises environment. Nowadays, I use Kemp LoadMaster as an application load balancer for SQL Server, DNS servers, and different applications where load balancing is possible.

The most valuable feature of the solution is the Edge Security Pack (ESP). With Edge Security Pack (ESP), you can have your internet connections checked against the authorizations, functionalities, and the pre-authorization that happens when you access resources from the internet that are hosted internally so that no one can access these services without authentication.

We use our devices as virtual load balancers for Exchange 2016, primarily.

We have two sites with two LMs at each site in clusters. We also use the devices as global DNS services and reverse proxy/authentication servers for our external users.

Our services are primarily Microsoft products being served. These include Exchange, SharePoint, CRM Dynamics, Skype, and ADFS. We are also looking at implementing websites in the future as required.

SSL offloading is enabled. Our devices are set up in the network as well as the DMZ.

With Kemp, I have been able to implement a global DNS load balancer between two sites for internal and external users with our existing Exchange DAG setup. This has made DR and BCP much easier to manage.

Our previous setup used Microsoft's TMG solution, and when that went end of life we needed to figure out a replacement. Being able to use load balancing, SSL offloading, and Edge Security Packages, all in one service, made my life much easier to manage from a day to day and single pane of glass perspective.

We use the Kemp Load balancer with our on-premise Exchange 2016 using two servers on a DAG at different locations. The Kemp load balancer allows us to have a hands-off failover between servers either in a Disaster Recovery model or during upgrades for security patches or service pack updates for the Exchange software.

We are now expanding this for our corporate webserver that will also be hosted at both of our locations. We have more confidence in having on-premise applications than trusting the Cloud. 

Our organization is better protected from an email outage than before. The old process of manually having to redirect Outlook Web Access traffic and Email traffic to a second server is a thing of the past.

I can sleep at night because of the Kemp Load Balancer, just knowing that in case of a failover, the email will keep flowing and our users will have access in the morning.

Having near 100% uptime for email is critical. Without email access, we would lose business

I used it as a front end to an RDS Farm. Its load-balancing port 80 and port 443 to multiple RDS Gateways. It's deployed as a virtual appliance on an on-prem virtual machine hosted on the Hyper-V server. Kemp LoadMaster is used by more than 1,000 internal users on a daily bases to access the application system at the back end. It's not exposed to the internet, it's used only from internal users inside the corporate LAN. We have daily VM backups setup as well as application backups from inside KEMP.

We used to have DNS round-robin based load balancing from some small applications but it was not highly available and if one instance were to do down half of the traffic would go down. We have tested the build it Microsoft Load balancer, but it was free and it was not reliable. Currently, we are using ZEN NLB for a few small applications that do not require many features but when it came to having a proper NLB for 1000 users the ZEN NLB could not handle the load. We have tested F5 and Kemp and Kemp were much cheaper and easier to setup.