I previously used an open-source version of this solution, but it was very hard to maintain and suffered frequent crashes, so we switched to Kemp for better reliability. I also used Citrix, but the use case for it is completely different than for Kemp.

I have used ZEN NLB and Microsoft NLB.

We switched from a prior solution since the LoadMaster provided the features, performance and throughput that we required for a more affordable price point.

Prior to Kemp LoadMaster, we used end-of-life products from Microsoft.

Kemp was my first experience with load balancers.

We did not previously use load balancing, Kemp was our first choice.

We used NLP, which is not in the same leak. That's a Microsoft inbuilt network load balancer, but it's not in the same leak. It doesn't do the application-level low balancing.

Yes, because we were upgrading the entire organization's Exchange version and we wanted a better, HA Clustered solution to match the Exchange redundancy we had built.

We used DNS Round-robin and some manual intervention but it was unreliable and very time-consuming. 

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

I did use the Microsoft TMG server, but its tech support expired and is no longer available.

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

Prior to this, I had a product from Cybonet called PineApp.

It is supposed to perform as a  reverse proxy and synchronize emails to mobiles phone and Outlook but I had a lot of issues and it did not work smoothly. I asked them to suggest to me what to do and they told me that they can only handle 20 to 30 users. They said that if I wanted me then I need to purchase another dedicated product.

I was not satisfied and this caused me to replace it.

We were using Simple Failover, but it was running into issues and we were looking for more of an enterprise solution.

We used to work with Windows NLB, and we switched to Kemp to meet a higher level of stability and quality of service.

Microsoft Threat Management Gateway. Product is at its end of life.

We tried a few products and they were expensive and overly complicated.

Kemp was our first product to use.

We used Citrix Netscaler prior to this product.

We haven't tried any other solution.

I switched because Kemp LoadMAster is more efficient, stable and scalable than the other solution.

We have another solution in place and we are currently planning to retire it, now that Kemp has been implemented.

Previously, we had been using a Barracuda load balancer. It was nice but the management was not as easy to use and it was not quite as reliable as we would have liked.

This was the first solution of this type.

Microsoft LB and was recommended by a Vendor we used for a project. 

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

We did not previously use a different solution.

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

We did not use another similar solution. There is no alternative advice; we heard that Kemp is the best load-balancer.

This is the first such solution we have used.

Previously we were proposing Citrix NetScaler or F5. We switched due to cost.