Kemp LoadMaster Reviews

We use this to load balance internal and external IT systems ranging from a few connections per minute to well over 10k connections per minute.

We also leverage the Global WAF features that Kemp offers.

We run these LoadMasters in an HA environment, to better allow for failovers and increased uptime. We use to balance HTTP/HTTPS traffic on the public internet for public sites, some with near 0k connections per minute. We also use to balance internal IT services such as LDAP, LDAPS, and DNS through various VIPs. 

Kemp has greatly improved our uptime, reduced time we spend on maintenance, and increased the reliability/trust we have in our load balancing system.

We had issues with the network architecture that was needed with our previous balancing system, and we found that we could run a much simpler network setup with the Kemp HA pair.

We can now avoid scheduled downtimes for infrastructure events, through the use of Kemp's HA setup and multiple real servers behind each VIP.

HA failovers are seamless and have allowed for a huge improvement in agility and flexibility in our environment. 

We leverage HTTP/HTTPS  load balancing, WAF, and DNS load balancing the most. We have found Kemp to be the most reliable for these services and have not had any issues at all.

The Global WAF has saved us more than one time from unwanted traffic.

HTTPS/HTTP balancing has been smooth and Kemp handles extremely high traffic loads with ease. We really also like the ability to do LDAP/LDAPS balancing for our internal customers.  This allows for a more smooth experience for our end users and for our internal applications.  

The one area that really could be improved upon is the GUI. Over the last several major versions, the GUI has remained virtually unchanged and still seems lacking. Since there is no "save" or "confirm" button, it is very easy to accidentally make a change on a live, production VIP, or endpoint.

Adding some sort of saving or confirming mechanism in the GUI would be nice and would make it seem more modern. This is not a show stopper for us, but really just a "nice to have". 

Overall, there is little that needs to be improved with this product. 

We have been using Kemp LoadMaster for six years.

They are very stable and reliable. We have had no issues at all over the last six years.

This product is very easy to scale up and grow. If in an HA pair, it can be done without downtime.

Support is a ten out of ten. They are quick to answer and very knowledgeable from the start.  They are far better than other IT vendors I have worked with.

We are using Kemp as a reverse proxy for Microsoft Exchange. We are also using the product for load-balancing internal services.

The Kemp virtual appliance is installed in the DMZ and forwards the traffic to the internal servers. We configured the Edge Security Pack (ESP) so that the virtual appliance captures the credentials of the user, validates those against the authentication services, and then lets the user pass through.

Using this solution, it doesn't publish Exchange servers directly over the internet, thus providing security.

Having a reverse proxy is a secure way to protect access to inside services like Microsoft Exchange. With the ESP configured, we feel that the services are more protected from external threats. There's a lot of attacks possible on Exchange and we needed a solution that would prevent direct access to the web interfaces.

Having the virtual appliance sitting between the internet and the real servers, it intercepts the requests, process them, and can block unwanted requests with the Web Application Firewall.

The most valuable feature is the reverse proxy with ESP since it protects forms and provides authentication of web services. 

When you configure the listening services, you can implement a lot of security features like the Edge Security Pack that intercepts the requests and processes those before they are sent to the real servers.

There's an integrated Web Application Firewall module that you can activate to protect your online services. The module has an auto-update feature, where Kemp pushes the latest rules automatically to protect you against new threats.

The configuration of basic services is pretty straightforward but when you want to configure more advanced settings like the Edge Security Pack feature, it can be somewhat challenging! Even with the documentation, I had to contact the support to get help set this up properly. I think there should be more visual instructions on how to configure advanced features.

Support-wise, I've nothing to complain about. The support technicians are knowledgeable and were able to quickly help me set up and get things working.

The logging feature is somewhat archaic, as you have to go through text files. I think they should implement something more user-friendly for logging.

We've been using Kemp for several years. We used the physical appliances for about five years and we recently switched to the virtual.

We've been using the product for several years and it never crashed.

This product is pretty scalable with the virtual appliance.

Great support, fast and really professional.

Kemp was the first solution we used as a reverse proxy.

The initial setup was pretty straightforward.

We implemented in-house with help of Kemp support.

Nowadays, going with the virtual appliance is the easiest way and the cost is reasonable.

We did not evaluate other products before choosing Kemp. Instead, we looked at product reviews before purchasing.

We currently use multiple Kemp appliances to load-balance the delivery of email to our CAS\Mailbox environment.

Previously, we had multiple CAS servers and Mailbox servers and Kemp was handling that environment greatly. We also used it to migrate to a Single CAS with multiple DAGs. The process was very simple on the Kemp side.

We also are using it to assist us with uptime due to any possible maintenance windows we have and/or any troubleshooting with the server environment. Kemp allows us to reboot servers and not affect mail delivery, as it will still deliver to a different node.

LoadMaster has greatly helped us with the uptime of our email services. If one server is having issues, it will still deliver to another server.

Using this product also made it easier to handle migrations to newer Exchange services because the product was the main point of communication, which meant that changes on the device affected everything. This made things simpler for us.

Not spending hours on troubleshooting issues, Kemp support resolved issues quickly.

The load-balancing is the biggest feature, of course. It just works. If one CAS goes down, Kemp will still deliver to the other server. It is the same with multiple mailbox servers. If one goes down then mail can still be delivered, due to the fact that Kemp is handling the communications.

Updates are easy to apply and don't cause downtime as long as you have two load-balancers. 

The product also allows us to limit certain services on the Exchange server. Allows more control and Access Control Lists (ACLs) for internal and or external access. Instead of making changes in IIS on a server, you can have Kemp control it.

Obviously, there are a lot of moving parts and fields\settings on Kemp LoadMaster. Not all the settings are easily understandable. It would be helpful if there were a way to incorporate tooltips on the fields so that we don't have to dig through documentation.

I don't expect the software to assist in migrations, but it would be a plus if they had more documentation on Exchange migrations with Kemp and specific changes that need to be made. However, support is very knowledgeable and assisted us.

I would like to see an increase in the knowledge base on technical issues or common troubles.

We have been using Kemp LoadMaster for one year.

We have used the product for multiple years and haven't had any issues or outages from it, so downtime was never an issue.

This product is highly scalable.

Technical support is A+. They were great in our migration process and even went to assist us with questions that we had on Exchange.

We did not use another similar solution prior to Kemp LoadMaster.

The initial setup is straightforward.

The vendor, Kemp, assisted us and they are very knowledgeable.

It has paid for itself after multiple years. 

Any decent product will cost money and if you want great support and a great product, then you will want to spend the money on it.

We did not evaluate other products before choosing this one.

Our use case included product testing on how to configure the load balancing products.

My primary use case is to deploy the load balancer. We provide the deployment professional service to the end-user. Due to Singapore's government policy, government sectors do not allow the connection of the internet. Therefore, we will be the hands and legs of the Kemp professional service. We will seek advice from the Kemp professional service team before and after every time we onsite to the customer's site.

As a partner of Kemp Technologies, we're using the load balancers as a demo and testing environment. This helps us in providing product issue support for load balancers.    

Other than that, the demo is also conducted during product introduction, pre-sales stage.  

Next, we also conduct feature testing on Kemp's load balancing products.   

Functional testing is done on our environment before we implement to a customer's environment. Other than that, we can also try to simulate the customer's issues when we were handling support cases.  

The most valuable feature that I found is the load balancing feature, it is the core function of the product.   

The load balancer is stable and met the customer's expectations. So far, there have not been any issues reported on the basic load balancing functions.  

Besides that, there is also a load balancing mode that fits into the customer's requirements. This also gives more choice for the customer to change their load balancing mode in the future due to the yearly improvement of the audit requirement.   

I would like to give some advice on security improvement:

• First, is the password complexity's restriction. For example, there should be a password restriction policy on the password that only can be made up of a minimum of 12 alphanumeric characters with upper & lower cases.
• Second, is the password age restriction. For example, the password should be changed at least every 90 days.
• Third, the password history restriction needs improvement. For example, the password policy will restrict the user to always use a unique password combination. The password should not be reused for a minimum of three generations of passwords.
• Last but not the least, the default administrator account should be able to rename. This is to prevent a hacker to use brute force attack on the known default administrator ID.
  

I have been using this solution for more than one year.

We have fewer issues reported from the end-user. The support response is fast.

So far scalability has been good.

Technical support is good. So far every case is handled properly.

We did not previously use a different solution.

We implemented through the vendor team. They are very experienced.

The client required an infrastructure solution for the internal development team that was complaining regarding the performance and issues with the previous open-source solution. The usual infrastructure staging/development/production is available to the development team. Kemp LoadMaster serves as the internal load balancer for the application and web security layer with the Intrusion Prevention (IPS) and Web Application Firewall (WAF) that replace the opensource solution previously implemented.

Kemp LoadMaster has definitely reduced the complaints from the development team since its deployment. Even the administrators/support are pleased with the intuitive administrative portal and ease of usage. In terms of stability, the application is much more reliable and the security feature of Web Application Firewall (WAF) fully has the auditor requirement. With the virtual version of the Kemp LoadMaster, it was simply carving a virtual resource to spin up a virtual instance to test or put in use for another section.

The base feature of Kemp LoadMaster load balancing ticks all the boxes but the most valuable features would be the security features Intrusion Prevention (IPS) and Web Application Firewall (WAF). Both the features are not only reliable and stable but being an integrated solution makes troubleshooting and pinpointing the issue much easier than fumbling around on different devices/logs. The RESTful and PowerShell APIs are definitely come handy in this automation era and makes network development easy.

Overall, the Kemp LoadMaster has been an all-rounder great product and stable. The free trial and virtual edition make it a breeze for any potential customer to give it a spin before actually deciding to put it on the infrastructure or even talk to the CFO. Kemp could create a more structured lab oriented training program as part of its certification bundled with an online cloud lab that makes it easy for a client to learn and try out the Kemp LoadMaster immediately. The sales team would also benefit from this cloud lab service.

It has been roughly about a year plus since the solution was deployed for the client.

The Kemp LoadMaster perform extremely well and stable during the POC testing and actual going live with the users.

Very scalable product.

Technical support is smooth and responsive.

We previously used a different solution and we switched mainly due to cost restriction.

Straightforward setup.

The deployment was done through a vendor team.

There must be a balance between cost and features. Going opensource usually goes up in terms of learning/training cost.

We evaluated F5, HA proxy, NGINX.

The primary use case of this solution is for load balancing websites, load balancing Citrix solutions, and load balancing Microsoft Dynamics.

This solution has helped us in certain situations that we have had to find a way to work around.

I like the way this solution handles multiple SSLs in different domains while still load balancing. I find that to be a very interesting feature.

It should be more customizable and perhaps more like NetScaler in that regard. Although Kemp is very user-friendly, it lacks a more custom configuration.

I would like to see this solution more customizable in the next release.

I have been using this solution since May of 2019.

This solution is stable. It's pretty good.

This solution's scalability is pretty good.

We have about 200 users in finance, customer service, and IT.

We are using this solution every day and we have plans to increase our usage.

The support is great.

Previously, I had used Microsoft NLB. We switched because it was more difficult to configure and it had many issues.

The initial setup was straightforward. It was very intuitive and user-friendly. The application itself is built to be more user-friendly.

It took two days to deploy. It wasn't difficult and it involved checking the configuration and calling support. There was no different kind of strategy.

It only takes one person to deploy and maintain this solution. As the Networking Administrator, I am the person who is responsible.

We did not use an integrator, reseller, or consultant. Only the main support.

Licensing is yearly and I am going to guess that it is CAN $2000.00.

There are no costs in addition to the standard licensing fees.

Check for the complete needs of your entire network system.

In order to configure things, you will have to first draw out your connections before you implement it.

This solution is good and it's reliable but there are things to improve.

I would rate this solution an eight out of ten.

Our primary use case is for load balancing traffic for solutions such as Exchange and Skype, as well as for web servers using HTTP and SMTP.

Another team is in charge of operating this solution.

We would like to see them improve the security by putting a well trusted and very efficient WAF inside the appliance. They currently use an open-source solution for this, but it would be great to include a more secure one because it would be a complete solution in terms of load balancing and security. We are currently researching WAF solutions to implement for our perimeter, so it is on the radar for our model.

The GUI is rather technical and complex, so it could be improved by making it simpler and more user-friendly. This is a very powerful solution that gives you an edge, but some of the features are hard to understand. For example, the configuration values are difficult. The templates help in this regard. Each value is explained in the documentation, but it still needs to be simpler.

I would like to see Active Directory integration for authentication of the admin role, so the usernames are not on the local appliance.

This solution is very stable. If I had to rate it out of ten then I would give it nine-point-eight.

We have the virtual appliance rather than the hardware, so in our case, scalability is easy. It is just a matter of licensing. If you want to add more CPU and RAM then you just upgrade your license and give the virtual machine more resources.

For the hardware appliance, my understanding is that it can scale depending on the environment.

They even have software that can turn any bare metal server into a hardware appliance.

We have six deployments across six offices, and in total there are approximately four thousand users. We do have plans to increase usage as we consolidate some of the servers in our private cloud. This will mean that more users are hitting the same office.

The technical support is great. They are knowledgeable on the technical level, responsive, and give you the solution very quickly. The troubleshoot the issue until the problem is solved.

They communicate by email and by phone and can log in remotely. They send us updates about new versions. 

The initial setup of this solution is simple.

They have very good documentation available on their website. The have templated well-known applications to help with load-balancing, and these help you a lot. One example is that they have templates for Exchange.

The return that we get for the money that we pay is very high.

This cost of this solution is not high, and cheaper than their competitors.

The license varies according to the number of megabits. For example, a 200Meg license can handle two hundred megabits per second, concurrently. If you need more then you just upgrade the license.

This product does what is advertised.

In terms of the value you get for the amount of money you pay, this is the number one solution.

For anybody who is implementing this solution, there is nothing to worry about. This product is mature, the documentation is there, and the support is very good. My recommendation is to get the virtual appliance instead of the hardware because it is easy, and that's what we have experience with. You get the same features and it is easy to scale and add more resources.

I would also suggest taking a backup of the configuration just in case they misconfigure something later. It is a complex configuration and if something goes wrong when somebody is changing it, it will break the traffic. You should be very careful when making changes to the configuration.

I would rate this solution a nine out of ten.

We implement it for our customers and we have every different version available from Kemp. The primary use case is for load balancing for different applications, mostly Microsoft Exchange. We use the on-prem deployment model.

The security features are the most valuable features of this solution.

It works very well. It's a good product that has good support. 

It is very stable.

It's very scalable. There are solutions for small customers and very large customers available from Kemp. In terms of users, we have different customers. The largest customer has about 5,000 co-workers.

We are satisfied with technical support. 

The implementation is not complex. The deployment took one day. 

The price is fine for their solution and what they give back from the product.

I would rate this solution a nine out of ten. To make it a perfect ten out of ten it would need better connection logging. If there is an active connection, then there is better logging. It should also have better management monitoring tools. 

They have great technical documentation on their website. That would be my recommendation if someone needs to implement Kemp Technology products.