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.
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.
I have worked with Kemp products for at least 10 years, as a consultant. In most cases, they are used for load balancing Exchange environments, but also as reverse proxies for other workloads such as Skype for Business, ADFS, etc.
The customer environments vary greatly. In most scenarios, it’s up to 2,000 users but in some cases more than 30,000. My last case involving Kemp was an Exchange 2016 site-resilient solution with 12 servers for 35,000 mailboxes.
Kemp Loadmaster gives our customers an easy and cheap way of load-balancing their workloads and adding reverse proxy for added security. With Kemp 360 Central, they get a nice overview of their Kemp products and an easy way to upgrade firmware on all devices from a single interface.
Kemp products are extremely stable and meet most of my customers' needs for an ADC solution. My customers appreciate the attractive pricing, stability. and user-friendly interface. The more advanced features such as WAF are rarely required by our customers.
Their virtual products are easy to install and easy to configure.
There are plenty of features that are lacking in my opinion:
Kemp support is great. You always get qualified assistance and the support engineers are friendly and helpful. You can find loads of information on the support website, including deployment guides for almost any workload.
I rate it at eight out of 10. There are many features that are missing or poorly implemented and things that you simply cannot do. The product is very much “as is”, and people need to be aware of that. If you don’t want these limitations, there are other products on the market, but they are typically a bit more expensive. Kemp products are very good load-balancers but are lacking in features compared to its competitors.
We are using Kemp Virtual LoadMaster for Microsoft Exchange load balancing, Skype for Business reverse proxy, and Oracle Forms load balancing.
For Skype for Business, we were using Microsoft TMG which is now end-of-support. Then we tried to use IIS as a reverse proxy but that feature was not suitable, especially on video calls where there were many issues. When we started using KEMP, we didn't face a single connectivity or delay issue on Skype for Business.
Previously, when we had maintenance on Exchange Servers, we had to take downtime. Also, whenever there was a glitch in the network our cluster got shifted to the secondary node. With KEMP, we don’t have to take any downtime for maintenance nor do we face any Outlook disconnect issue when there is a network interruption.
The load balancing for Exchange and reverse proxy for Skype are the features I like about it so far.
Reporting and monitoring need serious improvement.
Having LDAP authentication from the LoadMaster to the AD.
Edge Security Pack, because of the way it differentiates between critical infrastructure and the public internet. That, I think, is essential.
They need to improve the UI environment. Currently, it's hard to navigate and use product.
No issues with stability.
No issues with scalability.
I would rate tech support at nine out of 10.
This is the first such solution we have used.
It has a great price for the solution they offer.
We evaluated Azure but we preferred Kemp.
We do not use this solution on AWS.
When patching Skype for Business Enterprise, we experienced no downtime at all for internal users.
There is a Forefront TMG replacement together with Skype for Business which even Microsoft recommends for DNS LB. However, customers require uptime, and my tests show that DNS for external users will have quite long time downtimes versus HLB.
No issues. It is stable.
No issues. On the VLM, just update the license.
Technical support is very good. They are quick to answer questions and provide online help.
Simple to install with good documentation. Some documentation is out-of-date versus the new version, and things have been moved.
I have control on the licensing and all the prices since I work for a partner.
KEMP gives away free trials for 30 days. This can be stretched if you want. During the test, you will have access to KEMP support.
We looked into F5 BIG-IP. However, for small customers, they can't pay for four to five days do to basic config.
Look into what you need. Do you want to use virtual (VLM running on Hyper-V or VMware) or physical (LM)?
Load balancing to server farms upon response time performances. Usage of Web Application Firewall module.
There is a simplicity to the setup and configuration. It helps with efficiency and reactivity, in case of assistance needs.
The trio: Simplicity (no needs for many days of training) and a very attractive ratio of price/performance.
SNMP and/or RESTCONF management, in order to collect many counters, for plotting in a central application need to be improved.
High-availability, reverse proxy and web application firewall (WAF) for IoT devices and back-end web services. We have not fully enabled the web application firewall functionality as of yet, but plan to do so in the coming weeks.
Easy of Deployment. Application Delivery Controllers are not my company's strong suite. We needed a Microsoft Threat Management Gateway server replacement solution for a customer and were impressed with the simplified deployment of the Kemp LoadMasters.
I am small business and cannot afford dedicated consultants for one specific technology. I am able to leverage existing skillsets to deploy and configure the Kemp LoadMasters.
I do not feel we have enough experience with the product to talk to areas improvement or recommended features release.
Some of the support documentation seems to make assumptions that the person installing or configuring is experienced with the product or concepts. Further research got us through the installation and configuration without any issues.
No issues.
No issues.
High. They have a very responsive support.
Microsoft Threat Management Gateway. Product is at its end of life.
The initial deployment was straightforward.
For a cloud proof of concept, I reached out to Kemp support to help us with a multi-NIC VM deployment. Their support was fantastic and we were able to get up and running in short order. The downloadable templates were a huge time saver.
In-house.
Saved a third of the costs without sacrificing needed features by going with Kemp.
Download Kemp's VLM trial and take it for a test drive; you will be impressed.
Yes, Microsoft Web Application Proxy and F5.
My company is an IT Services Consulting company, and when requirements warrant, I plan on recommending Kemp to our other customers. Note: We currently have no financial interest in recommending Kemp.
