What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
ESP gives us peace of mind because it has taken over from Microsoft's Threat Management Gateway (reverse proxy) solution. It also alerts us if there are attempted security breaches so that we can be sure we are safe.
The DNS Load Balancer makes it so that I don't have to worry about site failures. As it manages both our external DNS and internal DNS queries, we can failover to the individual sites as required. This is true for site failures as well as planned maintenance.
We also use the Kemp 360 Vision, which monitors our services from an external perspective and alerts us via SMS and email, so I know if things go down.
What needs improvement?
We experienced a brief period of instability.
For how long have I used the solution?
We have been using Kemp LoadMaster for six years.
What do I think about the stability of the solution?
I have only had an issue with the solution once in terms of stability. The issue was not an end user-visible issue, and upgrading the O/S fixed the issue right away.
What do I think about the scalability of the solution?
I beleive it's scalable because I can always upgrade my licensing to a unit that handles more requests.
How are customer service and support?
Service is great, easy to work with, and always responsive.
Which solution did I use previously and why did I switch?
Prior to Kemp LoadMaster, we used end-of-life products from Microsoft.
How was the initial setup?
The initial setup is straightforward, due to Kemp's support services and available templates and documentation.
What about the implementation team?
We completed the setup in-house.
What was our ROI?
I believe it is high due to the many services that the solution has been able to provide.
What's my experience with pricing, setup cost, and licensing?
From a cost perspective, Kemp is very competitive and is not hard to justify by any means.
Which other solutions did I evaluate?
We looked at Citrix Netscaler as well as a solution by A10 Networks.
What other advice do I have?
My advice is to use Kemp's support to help with the initial setup. It is included in the initial cost and it makes sure that best practices are used. Keep up with the support because it's worth it.
I am currently happy with everything.
Which deployment model are you using for this solution?
On-premises
*Disclosure: My company does not have a business relationship with this vendor other than being a customer.
